Bug 59814
| Summary: | Reduce amount of tree traversal after DOM manipulation | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Roland Steiner <rolandsteiner> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | dglazkov, dominicc, eae, morrita |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | |||
| Bug Blocks: | 72352, 59802 | ||
Roland Steiner
After an operation that manipulates the DOM (node insertion or removal), we traverse the affected subtree twice: Once for setTreeScope/DocumentRecursively, and once for insertedInto/removedFromDocument/Tree(). We should be able to combine the updates into a single traversal.
Note that this applies to DOM manipulation outside of shadow DOM as well, but shadow DOM exacerbates the problem.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Dominic Cooney
This will be too complicated because the insertedInto/removedFromDocument/Tree callbacks will need to deal with TreeScope state that is not globally consistent.