No, label/inputs do not constitute a group of controls. A field set
would make sense if you grouped fields like address, zip code and
country inside a field set with a legend like "Your location".
I'm -1 as this is misleading.
> No, label/inputs do not constitute a group of controls. A field set
> would make sense if you grouped fields like address, zip code and
> country inside a field set with a legend like "Your location".
>
> I'm -1 as this is misleading.
Clearly, the <p> tag is the wrong tag. If an input and a label require
a wrapping container at all, what options do you have? <p> is for
*paragraphs of text*.
I agree with that - there should always be a div.field. This is
related to another discussion:
http://groups.google.com/group/rubyonrails-core/browse_thread/thread/a03d3e9d4014683c/3c844528ec21221d
Jonathan: I agree on the class="field". It's how I normally do it. I
do it to differentiate from <div class="actions"> where I include
submit buttons (and other form actions).
I'd be happy to re-do my patch (1760), replacing the fieldsets with
appropriately-classed divs, and then soliciting more feedback. Would
that make sense? Should we get more input before I do that?
Does it make sense to wait until things settle down with ticket 1626 first?