[Bug] Add key event check to is_tap_record
and remove is_tap_key
#18063
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.
Description
...as it is called with tick events and this would generate out of bound access
(col: 255, row: 255)
in keymaps inkeymap_key_to_keycode
though #13619 add a mitigation.. Unit-tests that previously failed are enabled again.is_tap_key
is removed as well because it is not used in the code base and subject to the same bug.Types of Changes
Issues Fixed or Closed by This PR
Checklist