You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Section 10.4, "Context" of content element reads:
"Where flow content is expected."
However, 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>
and have special content model like
, so if appears
directly under these elements, they become non-conformant (which should be
unexpected).
The definition of element (in Section 10.5) has the exact same issue.
Title: [Shadow]: usage in a place where non-flow content is expected (bugzilla: 22107)
Migrated from: https://www.w3.org/Bugs/Public/show_bug.cgi?id=22107
comment: 0
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=22107#c0
Yuta Kitamura wrote on 2013-05-21 08:06:43 +0000.
Probably related to bug 15616.
In Section 10.4, "Context" of content element reads:
"Where flow content is expected."
However, element should be able to appear in a place where non-flow
content is expected. Actually, an example in Section 11 illustrates such cases:
, so if appears directly under these elements, they become non-conformant (which should be unexpected).
The definition of element (in Section 10.5) has the exact same issue.
comment: 1
comment_url: https://www.w3.org/Bugs/Public/show_bug.cgi?id=22107#c1
Dimitri Glazkov wrote on 2015-04-23 18:54:48 +0000.
Doesn't need to block v1, nice-to-have.
The text was updated successfully, but these errors were encountered: