Fix #6279: prevent sending keymap or repeat info events by keyboards without keyboard capability #6697
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
vaxerski
reviewed
Jun 28, 2024
vaxerski
reviewed
Jun 29, 2024
…oards without keyboard capability
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.
Describe your PR, what does it fix/add?
This PR fixes a part of #6279, crashing of some programs.
Since this bug is caused by keyboards without keyboard capability sending keymap events or repeat info events, I have made changes to prevent it.
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
It may be an issue that such keyboards exist.
Is it ready for merging, or does it need work?
It is ready.