This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22107 - [Shadow]: <content> usage in a place where non-flow content is expected
Summary: [Shadow]: <content> usage in a place where non-flow content is expected
Status: RESOLVED MOVED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 15480
  Show dependency treegraph
 
Reported: 2013-05-21 08:06 UTC by Yuta Kitamura
Modified: 2015-05-27 02:43 UTC (History)
2 users (show)

See Also:


Attachments

Description Yuta Kitamura 2013-05-21 08:06:43 UTC
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.
Comment 1 Dimitri Glazkov 2015-04-23 18:54:48 UTC
Doesn't need to block v1, nice-to-have.
Comment 2 Hayato Ito 2015-05-27 02:43:27 UTC
Moved to https://github.com/w3c/webcomponents/issues/95