When I use a form_for, it''s adding an element class attribute on the form, which is mucking up the design. After some digging, I came upon this thread: http://www.mail-archive.com/rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org/msg61763.html Which appears to indicate that the class attribute is defined in the routes file. I don''t have any routes associated with this controller in my routes, so I guess it''s just adding a default value. How can I make this not happen? And if anybody would like to explain why it''s happening, I''d like to understand that. I am at a loss as to how this could be considered a good idea. Bill -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.