- From: <bugzilla@jessica.w3.org>
- Date: Tue, 21 May 2013 08:06:43 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22107 Bug ID: 22107 Summary: [Shadow]: <content> usage in a place where non-flow content is expected Classification: Unclassified Product: WebAppsWG Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P2 Component: Component Model Assignee: dglazkov@chromium.org Reporter: yutak@chromium.org QA Contact: public-webapps-bugzilla@w3.org Blocks: 14978 Probably related to bug 15616. In Section 10.4, "Context" of content element reads: "Where flow content is expected." However, <content> element should be able to appear in a place where non-flow content is expected. Actually, an example in Section 11 illustrates such cases: <div class="breaking"> <ul> <!-- The content model of <ul> is "zero or more li elements", which is NOT flow content. Therefore, the <content> below is non-conformant. --> <content select=".breaking"></content> </ul> </div> <table> and <tr> have special content model like <ul>, so if <content> appears directly under these elements, they become non-conformant (which should be unexpected). The definition of <shadow> element (in Section 10.5) has the exact same issue. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 21 May 2013 08:06:44 UTC