This now confuses me since Chrome behaves differently on Windows and Android. On this example https://codepen.io/SaschaNaz/pen/ZEyGQPR (You can open arrow button->Console to read it on mobile): * On Windows, when holding touch contact on the button, Chrome keeps the active state, just as Firefox does. * On Android, Chrome clears the active state. The timing is unknown, it does not clear during the context menu event or right after it, but some unknown time after that. I'm not sure this is even intended. :smaug, what do you think? I'm not sure what the patch should look like.
Bug 1724759 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This now confuses me since Chrome behaves differently on Windows and Android. On this example https://codepen.io/SaschaNaz/pen/ZEyGQPR (You can open arrow button->Console to read it on mobile): * On Windows, when holding touch contact on the button, Chrome keeps the active state, just as Firefox does. * On Android, Chrome clears the active state. The timing is unknown, it does not clear during the context menu event or right after it, but some unknown time after that. I'm not sure this is even intended. :smaug, what do you think? I'm not sure what the patch should look like. Maybe I should file the issue on Chromium instead?