Use KeyModifiers when implementing KeyMapping to match keyboard modifiers exactly#2804
Merged
Alexander Maryanovsky (m-sasha) merged 1 commit intoFeb 27, 2026
Merged
Conversation
Igor Demin (igordmn)
approved these changes
Feb 27, 2026
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.
Following https://android-review.googlesource.com/c/platform/frameworks/support/+/3940279 use
KeyModifiersto match shortcuts exactly in CMP too.Fixes https://youtrack.jetbrains.com/issue/CMP-7506
Note that technically, the windows bug was fixed in the AOSP CL, as the default (Windows/Linux) KeyMapping is defined in common.
Testing
Tested manually
This should be tested by QA
Release Notes
Fixes - Desktop