Bug 110353
| Summary: | Event dispatch should work even in disconnected DOM trees | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Dimitri Glazkov (Google) <dglazkov> |
| Component: | UI Events | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | annevk, jwalden+bwo |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Dimitri Glazkov (Google)
Anne, Olli, and myself discovered on #whatwg that WebKit has an odd quirk in regard to event dispatch: if the node is in a disconnected tree, the event is only fired on the node, and not along the event path. This is not the DOM Core specifies it, and apparently not how Mozilla's event dispatch works.
The quirk was introduced back in 2007: http://trac.webkit.org/changeset/19897.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
*** This bug has been marked as a duplicate of bug 81564 ***