This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
problem: option and optgroup elements are possibly missing "flow content" designation in the html 5 specification. I was concerned with the results of the HTML5 validator's results when it flagged my html 5 option elements as bad. I was using the w3schools.com states that to future proof your code you should close all your tags. in the spec http://www.w3.org/TR/2010/WD-html5-20100624/ , the option element is not specified using "flow content" designation, so it is therefore a singleton. so I used <option /> according to w3school's recommendation to use the xhtml style / to close singleton tags. this failed the validator. so either the validator is buggy, or the spec is missing the "flow content" designation. the dl and dt elements are specified as having flow content (which I think means having open and close tags) whereas before in my html 4.0 handbook they were singletons. the option tag and optgroup look like mistakes. they are missing all the "content" flags one would normally find (at least the flow content, if you are going to do dl and dt). I am just a user of html and a web programmer (actually a software engineer). so specifications to me are important. please fix either the validator or the spec. thanks.
I think I am wrong about the optgroup element. it seems to stand just fine without any child text. so why should it need flow content? I don't know it attributes are flow content or not, but it has 1 attribute. everybody seems to do option, dt, dl, and li tags their own way. why? because the fact that they are singletons or open/close is not clearly delineated in the spec. please make this clear in the html and xhtml and wml specifications. thank you.
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: Did Not Understand Request Change Description: no spec change Rationale: The flow content category has nothing to do with the "/>" style, which is only allowed on void elements, of which neither <optgroup> nor <option> are one. I'm not really sure what the problem in the spec is here.
mass-move component to LC1