Open Bug 1825949 Opened 2 years ago Updated 2 years ago

Earlier pointerenter events have later timesTamp than later pointermove events.

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

Firefox 111
defect

Tracking

()

UNCONFIRMED

People

(Reporter: isonon, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/111.0

Steps to reproduce:

  1. Add pointerenter and pointermove EventListeners to element.
  2. Move the mouse over the element.

Actual results:

pointerenter event has a later timeStamp than a later pointermove event.

Expected results:

pointerenter event has a ealier timeStamp than a later pointermove event.

The Bugbug bot thinks this bug should belong to the 'Core::DOM: UI Events & Focus Handling' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → DOM: UI Events & Focus Handling
Product: Firefox → Core

Indeed, at least enter event should have same or later timestamp of the source event for conforming to the meaning. However, we just create another instance without maintaining the timestamp.
https://searchfox.org/mozilla-central/rev/98397ff4eac3d32b815fbb33bff147297fb972d7/dom/events/EventStateManager.cpp#4413-4418,4422-4424,4426-4433

Smaug, what do you think? (At least, UI Events does not define timestamp about mouseenter etc.)

Severity: -- → S3
Flags: needinfo?(smaug)

We could just copy the timestamp from the *move event when generating enter/leave

Flags: needinfo?(smaug)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: