Bug 167021
| Summary: | Incorrect pointer-events:none passthrough to parent | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Darryl Pogue <dvpdiner2> |
| Component: | UI Events | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | cdumez, dino, graouts, jonlee, rniwa, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari Technology Preview | ||
| Hardware: | Mac | ||
| OS: | macOS 10.12 | ||
Darryl Pogue
Test case: https://jsfiddle.net/dpogue/p1bduqyo/2/
Clicking an element with `pointer-events: none` CSS should fire a click event targeting its parent. In this case, Safari fires the event on a parent higher up in the DOM rather than the immediate parent element.
Chrome and Firefox fire the click event with the correct parent
IE and Edge incorrectly fire the click event on the element (which is contrary to `pointer-events: none` behaviour)
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Lucas Forschler
Mass move bugs into the DOM component.
Ryosuke Niwa
Pointer events are UI events.
Radar WebKit Bug Importer
<rdar://problem/51920642>
Antoine Quint
Pointer Events != CSS pointer-events property. But yeah, this is probably the right component.