3 ms·
I think it is moving the cursor simultaneously with clicking that causes it. In other words the web-browser sees it as intention to mark / select content on web
by AgoRapide 6y ago
I think it is moving the cursor simultaneously with clicking that causes it. In other words the web-browser sees it as intention to mark / select content on web page.
Any suggestions for how to avoid this?
- wccrawford 6y agoThere's some CSS you can use that prevents selection. I can't see any need for selection in your app, so you could just apply it liberally.
- AgoRapide 6y agoThanks! I will look into it.
- AgoRapide 6y agoIt looks like adding "user-select: none" for the image tag did the trick. Please try it out now. (I do hope that the touch-interface was not affected by this, I only use mouse / keyboard myself).
- wccrawford 6y agoSeems good now. It also seems more responsive/snappier. That might just be in my head, though. It shouldn't affect touch events. That's a different CSS rule. Edit: Just tried it on Firefox/Android, and it seems like it actually changes multiple pages now. Perhaps it's reacting to both click and touch on mobile?
- AgoRapide 6y agoThat is possible, the touch interface is not that well tested. I will look into it.