You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was able to reproduce, the bug seems to be that the first tap on something that should be tappable isn't getting recognized, but all subsequent taps are. I'll look into this more.
the bug seems to be that the first tap on something that should be tappable isn't getting recognized, but all subsequent taps are.
Just a note here that I'm somewhat consistently seeing it happen on the same element (without taping something else in between taps), though I don't think this was shown in my demo video.
What OS are you using (
uname -a
, or Windows version)?Darwin MacBook-Pro.local 23.1.0 Darwin Kernel Version 23.1.0: Mon Oct 9 21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000 arm64
What version Socket Runtime are you using?
0.5.4 (97fa3f7c)
What programming language are you using (C/C++/Go/Rust)?
JS (Node v20.11.0)
What did you expect to see and what you saw instead?
Expect taps (on macbook pro's built-in trackpad) to work as expected
Taps only work sometimes as expected
Created an isolated test case: https://github.com/jaymakes11/ssc-reproduce-tap-bug
Created a demo video in that repos README (watch with video's sound turned ON to hear the taps).
The text was updated successfully, but these errors were encountered: