types: Add auxClick event types #4672
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JoviDeCroock
approved these changes
Feb 16, 2025
Member
JoviDeCroock
left a comment
JoviDeCroock
left a comment
There was a problem hiding this comment.
Love it when specs are in flux, todo sounds fine
rschristian
force-pushed
the
types/aux-click
branch
from
49cf59d to
1fc7423
Compare
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From the project referenced here: preactjs/preact-www#1240 (comment)
One thing worth calling out here is that the spec recently (-ish, 4 years ago) changed this event from extending a
MouseEventto aPointerEventand only Chrome/Chromium-based browsers support this yet. Do we want to make this aMouseEventwith a note to change this in the future, or usePointerEventnow (as this PR does)? I have no opinions one way or the other.