1871988 - Pointer event offsetX and offsetY are zeroed once the event has been processed

Status: RESOLVED DUPLICATE of bug 1359440

(Core :: DOM: Events, defect)

Description

[Nige White]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36

Steps to reproduce:

See this Codepen. Have the debugger open, it logs to the console.

https://codepen.io/Animal-Nige/pen/wvOBYMv

Click the Pen document. The event's offsetX and offsetY are logged, and then logged again a few milliseconds later.

Actual results:

The events offsetX and offsetY are zeroed in the second log.

Expected results:

The offsetX and offsetY should be just as persistent as clientX, clientY and all the other details.

Blink and Webkit both persist the values. The two console.log statements display the same values.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'DevTools::Debugger' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Nige White]

Attachment: The target event plus offsets defines the menu position.

The position upon scroll can only be recalculated if the offsets within the targetElement of the original event are preserved. I can work around this by caching them myself, but there's no reason to zero the offsets after the event has been processed.