Repository navigation
Conversation
Copilot
AI
changed the title
[WIP] Fix selection handles missing on double tap after multiselect
[WIP] Android: selection handles missing on double tap after multiselect — not yet reproduced
Oct 28, 2026
This branch has not been deployed
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
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.
On Android Chrome, double-tapping a word after a thought has been multiselected and then deselected is reported to select the word and show the Translate / Cut / Copy menu, but no selection handles.
This PR contains no code changes yet. The bug did not reproduce on
main(e1af1e0, the build the issue was filed against), so no cause has been identified and no fix or regression test has been written.Reproduction attempts
All runs used real-device Chrome 152 on BrowserStack, with taps sent as native device touches rather than synthetic events. Handles were detected in device screenshots.
- Lorem ipsum dolor sit ametLoremand ondolor; 400 ms and 1500 ms between steps)- Lorem ipsum dolor sit ametEvery intermediate step behaved as the issue describes:
dolorand opened the keyboard.dolor.Differences from the reporter's run
Needed to proceed