Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0f3
Issue ID
982363
Regression
No
[WebGl] TouchPhase.Stationary does not get called when receiving touch input
To reproduce:
1. Open project attached (touch input required)
2. Build it for WebGl
3. In your built project try touching and holding your finger
Expected: touch phases are updated - holding finger is
Actual: touch phases not update properly (check behavior in the Editor for comparison)
Reproduced in: 2017.1.3f1, 2017.2.1p1, 2017.3.0p1, 2018.1.0b2
Note1: TouchPhase.Stationary not getting called results in touch remaining in TouchPhase.Began until moved
Note2: TouchPhase.Stationary not getting called results in touch remaining in TouchPhase.Moved until touch ends
-
sssetz
May 12, 2021 18:19
I am also seeing this issue.
A work around is to just get TouchPhase.Began, and then flag some generic bool when that starts to true, and false on TouchPhase.Ended. Then you can atleast tell when touch is still happening, until this bug is fixed. Using Unity 2019 myself.
-
MichaelHVedeler
Mar 22, 2021 15:12
adding to previous comment, my scripts work fine in the editor when using touchscreen, but not when i have built it to webgl platform. I have even added at script that outputs a debug to show the current touchphase i am in. In the editor touchphase.stationary comes up, but in browser, the same as OPs issue appears..
-
MichaelHVedeler
Mar 22, 2021 15:09
Please review this bug again. Im experiencing the same issue. Touchphase.stationary seems to not be able to trigger
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
Resolution Note:
Desktop Team Management has evaluated this issue and determined that it does not meet our current bug severity threshold. If you would like your issue to be reviewed again, please re-submit your bug