3 ms·
The underlying problem here is that a click or tap should always refer to whatever _was_ on the screen a few (100?) milliseconds ago. It’s a long-standing bug o
by bryankaplan 11mo ago
The underlying problem here is that a click or tap should always refer to whatever _was_ on the screen a few (100?) milliseconds ago. It’s a long-standing bug on all platforms.
- hn92726819 11mo agoThat isn't a bug; it's working as intended. I do wonder if that could be mocked up easily in html to see what it feels like though. Sounds like a cool idea