[–] bhouser 2y ago ↗ I'm actually hoping I'm wrong about the inability to reliably distinguish between trackpad and mousewheel wheel events. [–] jeresuikkila 2y ago ↗ Secretly hoping to take advantage of Cunningham's Law?"The best way to get the right answer on the Internet is not to ask a question; it's to post the wrong answer." [–] bhouser 2y ago ↗ Well, yes actually.Except unfortunatly, I think I'm right.
[–] jeresuikkila 2y ago ↗ Secretly hoping to take advantage of Cunningham's Law?"The best way to get the right answer on the Internet is not to ask a question; it's to post the wrong answer." [–] bhouser 2y ago ↗ Well, yes actually.Except unfortunatly, I think I'm right.
[–] beardyw 2y ago ↗ Touch events per se are not supported in Safari as far as know. [–] bhouser 2y ago ↗ Interesting, didn't know that! Wonder why they don't.My issue here is with wheel events. They look identical for trackpads and mice, so I can't code for different behaviour.
[–] bhouser 2y ago ↗ Interesting, didn't know that! Wonder why they don't.My issue here is with wheel events. They look identical for trackpads and mice, so I can't code for different behaviour.
[–] MichaelZuo 2y ago ↗ i.e. Web apps can’t poll at 1000Hz or even 240. [–] bhouser 2y ago ↗ Is this an intentional browser API concession due to some polling limit? I don't see the connection?
[–] bhouser 2y ago ↗ Is this an intentional browser API concession due to some polling limit? I don't see the connection?
8 comments
[ 102 ms ] story [ 908 ms ] thread"The best way to get the right answer on the Internet is not to ask a question; it's to post the wrong answer."
Except unfortunatly, I think I'm right.
My issue here is with wheel events. They look identical for trackpads and mice, so I can't code for different behaviour.