# Rails3 form\_for adding element class...because...?

**URL:** <https://www.ruby-forum.com/t/rails3-form-for-adding-element-class-because/194750>\
**Category:** Rails\
**Created:** [September 9, 2010, 10:53pm UTC](https://www.ruby-forum.com/t/rails3-form-for-adding-element-class-because/194750 "2010-09-09T22:53:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![wbharding](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/8797f3/32.png) [@wbharding](https://www.ruby-forum.com/u/wbharding)\
**Post date:** [September 9, 2010, 10:53pm UTC](https://www.ruby-forum.com/t/rails3-form-for-adding-element-class-because/194750/1 "2010-09-09T22:53:32Z")

</div>

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/removed\_email\_address@domain.invalid/msg61763.html](http://www.mail-archive.com/removed_email_address@domain.invalid/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