| Summary: | Wheel events stop propagating when target element is removed from DOM | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Brent Fulgham <bfulgham> | ||||||||
| Component: | Layout and Rendering | Assignee: | Brent Fulgham <bfulgham> | ||||||||
| Status: | RESOLVED FIXED | ||||||||||
| Severity: | Normal | CC: | bfulgham, cmarcelo, commit-queue, esprehn+autocc, kangil.han | ||||||||
| Priority: | P2 | Keywords: | InRadar | ||||||||
| Version: | WebKit Nightly Build | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Brent Fulgham
2015-08-24 11:57:06 PDT
Created attachment 259762 [details]
Patch
Comment on attachment 259762 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=259762&action=review > Source/WebCore/page/mac/EventHandlerMac.mm:919 > + return false; Frames can be removed... > Source/WebCore/page/mac/EventHandlerMac.mm:922 > + return true; Anonymous nodes can't be scrollable? (probably true) > Source/WebCore/page/mac/EventHandlerMac.mm:925 > + return true; What if a node is moved around in the DOM? (removed and reinserted before we get here) Is that OK? Comment on attachment 259762 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=259762&action=review >> Source/WebCore/page/mac/EventHandlerMac.mm:925 >> + return true; > > What if a node is moved around in the DOM? (removed and reinserted before we get here) Is that OK? It does seem like it would be a problem if we removed a node from one scrolling container, and inserted it into a new location. In that case, even with this code, we would start our event handling with this "migrated" node. Maybe it would be better to just break the caching state in Element::removedFrom. Created attachment 259786 [details]
Patch
Created attachment 259797 [details]
Patch
Comment on attachment 259797 [details]
Patch
r=me
Committed r188920: <http://trac.webkit.org/changeset/188920> |