[web] limit preventDefault-ing of processed pointer events only for touchscreens#2973
Merged
Shagen Ogandzhanian (Schahen) merged 1 commit intoApr 13, 2026
Conversation
Oleksandr Karpovich (eymar)
approved these changes
Apr 13, 2026
Shagen Ogandzhanian (Schahen)
added a commit
that referenced
this pull request
Apr 13, 2026
…ouchscreens (#2973) We fight the undesired toggling of Virtual Keyboard view (caused by input losing it's focus) by prevent defaulting the pointer event if we know that compose processed it. Unfortunately this cancels out the drag-n-drop behaviour for nodes with both `clickable` and `dragAndDropSource` modifiers. The smallest, safest and quickest fix is just to revert to limiting this behaviour to touchscreens. This means that the DnD logic still won't work on mobile devices but this should be addressed separately ## Testing manual + `./gradlew testWeb` ## Release Notes ### Fixes - Web [CMP-10035](https://youtrack.jetbrains.com/issue/CMP-10035) dragAndDropSource combined with clickable doesn't allow to start drag
Vlad Konstantinov (Kpotko)
added a commit
that referenced
this pull request
Apr 13, 2026
…ouchscreens (#2974) This is cherry-pick of ff55f9c (see #2973) We fight the undesired toggling of Virtual Keyboard view (caused by input losing it's focus) by prevent defaulting the pointer event if we know that compose processed it. Unfortunately this cancels out the drag-n-drop behaviour for nodes with both `clickable` and `dragAndDropSource` modifiers. The smallest, safest and quickest fix is just to revert to limiting this behaviour to touchscreens. This means that the DnD logic still won't work on mobile devices but this should be addressed separately ## Testing manual + `./gradlew testWeb` ## Release Notes ### Fixes - Web [CMP-10035](https://youtrack.jetbrains.com/issue/CMP-10035) dragAndDropSource combined with clickable doesn't allow to start drag
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
We fight the undesired toggling of Virtual Keyboard view (caused by input losing it's focus) by prevent defaulting the pointer event if we know that compose processed it. Unfortunately this cancels out the drag-n-drop behaviour for nodes with both
clickableanddragAndDropSourcemodifiers.The smallest, safest and quickest fix is just to revert to limiting this behaviour to touchscreens. This means that the DnD logic still won't work on mobile devices but this should be addressed separately
Testing
manual +
./gradlew testWebRelease Notes
Fixes - Web
CMP-10035 dragAndDropSource combined with clickable doesn't allow to start drag