[TimePicker] Prevent mouse events after touchend event
#15346
+1
−0
Conversation
This file contains 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
arthurbalduini
added
the
component: pickers
arthurbalduini
changed the title
touchEnd
arthurbalduini
changed the title
touchEndtouchend event
arthurbalduini
added
the
needs cherry-pick
|
Deploy preview: https://deploy-preview-15346--material-ui-x.netlify.app/ |
LukasTy
changed the title
touchend eventtouchend event
LukasTy
added
regression
LukasTy
approved these changes
Nov 12, 2024
flaviendelangle
approved these changes
Nov 12, 2024
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.
Closes #15338
After the introduction of #14305 the addition of touchStart causes touchEnd event to trigger mouse events leading to the bug reported.
Unfortunately the test environment does not simulate this behavior, otherwise it would have been catched by this test
Since we do not expose the event handlers on this component, I wouldn't expect issues on preventing this behavior that is, although a bit weird, the correct one.
Could be cherry-picked to v7