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 20619 - [Shadow]: ShadowRoot
Summary: [Shadow]: ShadowRoot
Status: RESOLVED WORKSFORME
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:
 
Reported: 2013-01-09 13:31 UTC by Anne
Modified: 2013-04-01 23:20 UTC (History)
0 users

See Also:

Attachments

Description Anne 2013-01-09 13:31:58 UTC 
ShadowRoot inheriting from DocumentFragment and not being its own Node or standalone entity makes it participate in a number of algorithms defined in DOM, which does not seem entirely correct. E.g. appendChild() accepts ShadowRoot as currently defined. Or is that okay?
Comment 1 Dimitri Glazkov 2013-04-01 23:20:17 UTC 
(In reply to comment #0)
> ShadowRoot inheriting from DocumentFragment and not being its own Node or
> standalone entity makes it participate in a number of algorithms defined in
> DOM, which does not seem entirely correct. E.g. appendChild() accepts
> ShadowRoot as currently defined. Or is that okay?

Yep, that's the reason we went with a DocumentFragment. It provides the exact behavior we want for ShadowRoot.