Bug 267815
| Summary: | PointerEvent delivered to a pseudo inside a display:contents element yields unexpected results | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Nige White <nige.animal> |
| Component: | UI Events | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | a_protyasha, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari 17 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Nige White
Chromium has the same issue here: https://bugs.chromium.org/p/chromium/issues/detail?id=1518093
It would seem that Chromium inherited the issue from WebKit.
Run this and follow instructions: https://codepen.io/Animal-Nige/pen/qBvqxjz
Have the debugger console open.
Click in the center of the red box (#inner).
The event is delivered to #inner which is the first element at the mouse position to have a box in which to report offsetX/offsetY
But it reports offsetX/offsetY as pageX/pageY.
There's plenty of discussion on the Chromium thread. But I think this is a hole in the spec where rational behaviour needs to be decided and codified.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Nige White
No?
Radar WebKit Bug Importer
<rdar://problem/121737485>