This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-legend-element Comment: Suggestion: Deprecate Legend Element Posted from: 93.206.148.229
The Legend element is an artificial, nonviable construct, strictly bound to another element ("fieldset"), with no use other than applying a textual attribute to the <fieldset> element, imposing unnecessary declarative constraints and implementation trouble, not justifying the existance of this element as a stand-alone element. I suggest to deprecate the <legend> element in favour to replacing it with a more light-weight solution: a "legend" attribute, applied to the <fieldset> element.
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: How would you put a form control in an attribute? One of the use cases for <fieldset> is to have a checkbox in the legend.
I see... Sorry, didn't read the DTD correctly. My mistake.