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 16101 - [Shadow]: Consider the insertion points or shadow insertion points in fallback content can be active.
Summary: [Shadow]: Consider the insertion points or shadow insertion points in fallbac...
Status: RESOLVED WONTFIX
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Hayato Ito
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 15480
  Show dependency tree / graph
 
Reported: 2012-02-24 07:35 UTC by Shinya Kawanaka
Modified: 2013-10-24 07:45 UTC (History)
2 users (show)

See Also:

Attachments

Description Shinya Kawanaka 2012-02-24 07:35:08 UTC 
Current spec says: "The insertion points or shadow insertion points in fallback content must be considered inactive."

However, it may be useful if such insertion points can be active.

This is an example.
<content id="c1" select="#some-element">
    <content id="c2" select="#another-element">
    </content>
</content>

If #c1 doesn't select anything, we can try #c2 if #c2 can be active.
This enables us to write OR statement.
This cannot be written if using only comma separated value in select like: #some-element, #another-element, because if there are bother #some-element and #another-element, they will be all selected.
Comment 1 Dominic Cooney 2012-03-05 05:22:42 UTC 
This would be an increase in expressive power. I think it should be permitted.
Comment 2 Hayato Ito 2013-10-24 07:45:49 UTC 
Let me mark this WONTFIX until we have real use cases for this.

Please feel free to re-open this if you need this feature.

I think:
- we could allow content insertion points in any position in shadow trees.
- We could allow at most one shadow insertion point per a shadow tree.