Bug 71126
| Summary: | Shadow DOM throws WRONG_DOCUMENT_ERR | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ojan Vafai <ojan> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | abarth, dglazkov, dominicc, eae, rniwa, tasak, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 97279 | ||
Ojan Vafai
We are killing WRONG_DOCUMENT_ERR across the web platform. The only places WebKit still fires this event are in DOM Ranges and in shadow DOM's validation after http://trac.webkit.org/changeset/90026. The correct thing to do if the shadowRoot's document is different than the one it's being set to is to do the adoptNode.
See ContainerNode::insertBefore for an example. I believe it's the setTreeScopeRecursively call that does it.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Ryosuke Niwa
We don't do this anymore.
Radar WebKit Bug Importer
<rdar://problem/56003852>