This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In the section 4.10.1.1, 'Writing a form's user interface', the spec defines form controls as being individual paragraphs of a form: "Each part of a form is considered a paragraph, and is typically separated from other parts using p elements." I feel that it would be more semantically appropriate to utilize a new form "field" element for marking up form controls and to differentiate them from other, regular paragraphs. For example: <form> <field> <label>Name</label> <input /> </field> </form> This would also make the "fieldset" more applicable, as it could now actually be a set of fields.
An interesting notion, but not for "CR".
(In reply to Robin Berjon from comment #1) > An interesting notion, but not for "CR". Thanks, this was my first suggestion, and was a bit confused by the process of submitting it. Is there a way to get this out of "CR" and into whatever the correct spot is so that it can be considered?
(In reply to email from comment #2) > (In reply to Robin Berjon from comment #1) > > An interesting notion, but not for "CR". > > Thanks, this was my first suggestion, and was a bit confused by the process > of submitting it. Is there a way to get this out of "CR" and into whatever > the correct spot is so that it can be considered? Yes, don't worry, the confusion is entirely our fault and I've moved your bug to the right place!
(In reply to email from comment #2) > (In reply to Robin Berjon from comment #1) > > An interesting notion, but not for "CR". > > Thanks, this was my first suggestion, and was a bit confused by the process > of submitting it. Is there a way to get this out of "CR" and into whatever > the correct spot is so that it can be considered? Note, you might wish to discuss it on public-html@w3.org to get broader feedback.
HTML5.1 Bugzilla Bug Triage: This bug constitutes a request for a new feature of HTML. Our current guidelines, rather than track such requests as bugs or issues, is to create a proposal for the desired behavior, or at least a sketch of what is wanted (much of which is probably contained in this bug), and start the discussion/proposal in the WICG (https://www.w3.org/community/wicg/). As your idea gains interest and momentum, it may be brought back into HTML through the Intent to Migrate process (https://wicg.github.io/admin/intent-to-migrate.html).