Android: Double/tripple tap selection does not show the context menu

[personalizedrefrigerator]

Describe the issue

Steps to reproduce

1. Double-tap on a word in a CodeMirror editor.
2. Tripple-tap on a different line.
3. Long-press on a word in a CodeMirror editor.
4. Open the web inspector (remote tools via chrome://inspect) and delete the mousedown listener on CodeMirror's contenteditable element.
   
5. Double-tap on a word in a CodeMirror editor.
6. Tripple-tap on a different line.
7. Long-press on a word in a CodeMirror editor.

Observed behavior

• Steps 1 and 2 do not display a context menu, but steps 5 and 6 do.
• Steps 3 and 7 display context menus.

Expected behavior

As in other contenteditable regions, a context menu should open when selecting text with double/tripple-taps.

Environment

I experience this with extensions: [] and with the CodeMirror editor on codemirror.net.

Browser and platform

Chrome 104/Android 12; Android system WebView

Reproduction link

No response

[marijnh]

This is related to #645 , where we replace the native double/triple tap behavior with custom code because it often does unexpected things. Unfortunately, setting the selection programmatically seems to suppress the context menu behavior.

As with many things on Chrome Android, selection in response to tapping causes a whole cascade of different selection and composition events, and my attempt to add an after-the-native behavior check that adjusts the selection if it isn't what the editor would expect is turning out to be a lot less straightforward than I hoped.

Double-tapping a string of words with a period in it causes three different selections to appear in turn (cursor at tap position, word up to period, whole word string). Also, the compositions can cause CodeMirror to touch the content DOM, resetting the selection, and putting it back in place again kills the context menu. Going to look at this some more tomorrow.

[marijnh]

For now, I've decided to just allow double/triple taps to go through natively, since it seems having the context menu is rather important.

[personalizedrefrigerator]

and putting it back in place again kills the context menu

It may instead be calling .preventDefault that stops the context menu from showing up. See the workaround Joplin is currently using.