[Bug 10987] New: option and optgroup elements - flow content?

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10987

           Summary: option and optgroup elements - flow content?
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: jmichae3@yahoo.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


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.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 7 October 2010 06:22:30 UTC