3 ms·
That’s a classic issue with these, and often not solvable by the web developer - an issue with mobile browsers themselves that’s hard to get around
by jama211 11mo ago
That’s a classic issue with these, and often not solvable by the web developer - an issue with mobile browsers themselves that’s hard to get around
- animuchan 11mo agoIt's trivially solvable with CSS though, isn't it? See the beginning of this stylesheet for example: https://github.com/mvasilkov/board2024/blob/master/out/app.css https://github.com/mvasilkov/board2024/blob/master/out/app.c... — this is from my small 2024 game.
- ffsm8 11mo agoYou mean the select: none, along with the drag setting? If so, that's not necessarily followed/applied for accessibility reasons
- animuchan 11mo agoIf your game is essentially a single canvas element, having it user-selectable clearly doesn't help accessibility in any way.
- ffsm8 11mo agoYou say that as if I've got any control over the browser on the end users device, some of which will be configured to not apply these rules globally for accessibility reasons...
- jama211 11mo agoAlas no, it doesn’t solve it for all browsers/use cases.