15295 2011-12-21 09:10:11 +0000 [Shadow]: Clarify the intent of rendering content elements as fallback content of shadow elements and vice-versa 2011-12-21 20:15:24 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED FIXED P2 normal --- 14978 1 dominicc dglazkov public-webapps-bugzilla oldest_to_newest 61863 0 dominicc 2011-12-21 09:10:11 +0000 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. 61893 1 dglazkov 2011-12-21 20:15:24 +0000 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