ReaderHighlight: fix accidental tap while long-pressing#14004
Merged
Conversation
poire-z
approved these changes
Jun 30, 2025
poire-z
left a comment
Contributor
There was a problem hiding this comment.
Not obvious what could be the side effects, but ok.
0xstillb
pushed a commit
to 0xstillb/koreader-thai
that referenced
this pull request
May 9, 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.
While long-pressing (being a long press or a very long press), the device can detect an accidental tap.
In that case the hold state is lost, and the hold_release event cannot be handled.
If a very long press has been done, the pokeball icon remains on the screen.
Reported in #11514 (comment) and https://www.mobileread.com/forums/showthread.php?t=368795.
The fix: run
onHoldRelease()(what a user wanted when long-pressed).This change is