extend composition suppression to handle FlorisBoard-style deletions#2719
Merged
Conversation
Soxasora
approved these changes
Dec 27, 2025
Member
Soxasora
left a comment
Soxasora
left a comment
There was a problem hiding this comment.
I tested this on FlorisBoard, Yandex and AOSP keyboard.
This works and doesn't impact the other keyboards' functionalities, not even Desktop.
Thank you!
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
3 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.
Fixes #2718
FlorisBoard deletes text differently: it first selects the character to remove, then fires an
insertTextinput event withdata=''to replace the selection with nothing.The original PR didn’t account for this pattern, so this PR adds that case to the suppression trigger list.