Bug 267815 - PointerEvent delivered to a pseudo inside a display:contents element yields unexpected results
Summary: PointerEvent delivered to a pseudo inside a display:contents element yields u...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: UI Events (show other bugs)
Version: Safari 17
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2024-01-20 07:27 PST by Nige White
Modified: 2024-01-27 07:28 PST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nige White 2024-01-20 07:27:55 PST 
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.
Comment 1 Nige White 2024-01-25 23:18:24 PST 
No?
Comment 2 Radar WebKit Bug Importer 2024-01-27 07:28:11 PST 
<rdar://problem/121737485>