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 15295 - [Shadow]: Clarify the intent of rendering content elements as fallback content of shadow elements and vice-versa
Summary: [Shadow]: Clarify the intent of rendering content elements as fallback conten...
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 14978
  Show dependency treegraph
 
Reported: 2011-12-21 09:10 UTC by Dominic Cooney
Modified: 2011-12-21 20:15 UTC (History)
0 users

See Also:


Attachments

Description Dominic Cooney 2011-12-21 09:10:11 UTC
Is the intent for it to be possible to use content and shadow elements as fallback content for content and shadow elements?

The algorithm described in "Rendering Shadow DOM Subtrees" has two holes:

In the case of this shadow:

<shadow>
  <content id="a"></content>
</shadow>

When there is no older shadow tree, the algorithm hits this case:

2.(third bullet).2: Otherwise, render fallback content as any DOM subtree

ie since it does not specify "…but with the same rendering exceptions" this means that any nodes distributed to #a are not rendered. Is this intentional?

The opposite case:

<content id="a">
  <shadow></shadow>
</content>

when there are no nodes distributed to #a likewise specifies rendering <shadow></shadow> as any DOM subtree and not with shadow DOM rendering exceptions.

Likewise for

<content select="…">
  <content select="…"></content>
</content>

Could the spec provide commentary on whether the intent? And if the intent is that it is possible to use content and shadow as fallback content for content and shadow, the algorithm needs to be fixed to support this.
Comment 1 Dimitri Glazkov 2011-12-21 20:15:24 UTC
Tweaked the wording to explicitly state that fallback content doesn't get to play with insertion points.

http://dvcs.w3.org/hg/webcomponents/rev/4944c784494e