Skip to content

Conversation

@hamishwillee
Copy link
Collaborator

MouseEvent.movementX and MouseEvent.movementY state that the value is only set for mousemove event. In fact it is also set for pointermove on Chrome and FF, and pointerrawupdate on Chrome and FF from version 148.

This adds the clarification.

Related docs work can be tracked in #42752

@hamishwillee hamishwillee requested a review from a team as a code owner January 27, 2026 05:07
@hamishwillee hamishwillee requested review from wbamberg and removed request for a team January 27, 2026 05:07
@github-actions github-actions bot added Content:WebAPI Web API docs size/s [PR only] 6-50 LoC changed labels Jan 27, 2026
@github-actions
Copy link
Contributor

Preview URLs (3 pages)

External URLs (2)

URL: /en-US/docs/Web/API/MouseEvent/movementX
Title: MouseEvent: movementX property


URL: /en-US/docs/Web/API/MouseEvent/movementY
Title: MouseEvent: movementY property

Copy link
Contributor

@SebastianZ SebastianZ left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine to me from what I get from my tests and from Masayuki's descriptions. Thanks!

I initially thought that change should also be mentioned on the PointerEvent interface, but those two properties are actually part of MouseEvent and only inherited, so it is ok as is.

Sebastian

Copy link
Collaborator

@wbamberg wbamberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 thank Hamish, and Sebastian! Also, hi Sebastian!

@wbamberg wbamberg merged commit 14d2fab into mdn:main Jan 28, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Content:WebAPI Web API docs size/s [PR only] 6-50 LoC changed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants