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 15163 - [Explainer]: Multiple shadow DOMs make me :/
Summary: [Explainer]: Multiple shadow DOMs make me :/
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: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 14949
  Show dependency tree / graph
 
Reported: 2011-12-13 05:34 UTC by Divya Manian
Modified: 2011-12-21 21:31 UTC (History)
0 users

See Also:

Attachments

Description Divya Manian 2011-12-13 05:34:19 UTC 
It feels very tedious and complicated to have shadow parents etc for custom elements extending other custom elements. I think it introduces complications that might not be needed for a first draft of the spec?
Comment 1 Dimitri Glazkov 2011-12-21 21:31:26 UTC 
I agree! It would've been much simpler to not have multiple shadow DOM trees. In fact, I tried to resist having multiple trees for the longest time.

Unfortunately, without multiple shadows, it is impossible to clearly explain how to add shadow DOM subtrees to a bunch of built-in elements that already have shadow DOM-ish behavior. And so there we are :-\