[Bug 24754] New: menuitem and backward compatibility

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24754

            Bug ID: 24754
           Summary: menuitem and backward compatibility
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: major
          Priority: P2
         Component: HTML5 spec
          Assignee: dave.null@w3.org
          Reporter: master.skywalker.88@gmail.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org

http://www.w3.org/TR/html51/interactive-elements.html#the-menuitem-element
This element has "empty" as content model, in fact in the example it behaves
like other element with the same content model. I.e., there is only the opening
tag. But in the description it is not stated that the closing tag is omissible,
maybe for legacy browsers (the element wouldn't build a backward-compatible DOM
subtree as every subsequent menuitem is placed inside the preceding one(s). In
addition to this, Validator.w3.org/nu validates the menuitem expressed via
self-closing tag in XHTML documents, but in HTML document both <menuitem>
without closing tag and the self-closing slash are considered invalid (in the
former case the tag is considered still open, in the latter the error thrown is
[[Self-closing syntax (/>) used on a non-void HTML element. Ignoring the slash
and treating as a start tag.]]. Which is obviously inconsistent with the spec,
as the element IS void.
To both solve the background compatibility and the consistency issues, you
should:
 - either state that the tag is NOT omissible (and given the particularity of
this case I would suggest to highlight this issue) and correct the example
 - or correct the validator issues and the description, stating that the
closing tag is actually omissible but forcing the element inside a container
like a <p> or <label> element.
Otherwise, we'll end up having different requirements and different DOM trees
for HTML and XHTML and/or an unusable element due to lacking support in UAs.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 20 February 2014 21:24:16 UTC