Bug 70385
| Summary: | Implement full test suite for childList type mutation records | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Rafael Weinstein <rafaelw> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | adamk, ahmad.saleem792, ap, bfulgham, rniwa, syoichi |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 68729 | ||
Rafael Weinstein
There are a small number (maybe 10s) of cases where a single DOM operation can and should result in a single mutation record. We need to find these cases and assert their behavior in the layout tests.
Examples
-innerHTML
-innerText
-textNode.replaceWholeText
-node.insertBefore(node.firstChild, node.firstChild.nextSibling);
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Ahmad Saleem
We have WPT Test Suite - I don't think we would need separate test cases unless on rare occasions, Webkit is the first one to fix the issue or align with web-spec.
I am going to mark this as "RESOLVED WONTFIX" but if I am wrong then please reopen. Thanks!
Alexey Proskuryakov
Grepping through WPT tests that we have imported, I can't easily tell if these scenarios are covered.
But at least we work correctly in a few cases that I tried manually.