Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Movement controls occasionally get 'stuck' #1309

Closed
misslivirose opened this issue May 7, 2019 · 10 comments
Closed

Movement controls occasionally get 'stuck' #1309

misslivirose opened this issue May 7, 2019 · 10 comments
Labels
bug P2 Address when able

Comments

@misslivirose
Copy link
Contributor

This happens to me about once per week and we observed it today in one of the CHI viewing rooms - a movement control (I've been seeing this on desktop) gets stuck in a particular direction and you're stuck moving that way indefinitely. Sometimes, you can get out of this by repeatedly using the WASD keys to "unstick" but other times it requires a refresh.

@j-conrad
Copy link
Contributor

j-conrad commented May 7, 2019

Cross-linking to related issue(s):
#259 (comment)

@j-conrad j-conrad added the bug label May 7, 2019
@johnshaughnessy
Copy link
Contributor

johnshaughnessy commented Sep 5, 2019

We fixed parts of this issue:

  • you had to press SHIFT + the stuck wasd keyup (now you don't have to press SHIFT).
  • we clear the key presses on blur (so you stop moving if we receive a blur event).

This can still happen if you hold shift and then right click in firefox as outlined in #1263. We do not get contextmenu or click events when this overriding behavior happens, but we do get mousedown, so we could stop your movement on right mousedown + shift + firefox.

Then the only other way I know this behavior can happen is if we do not get a blur event when the user focuses a different application / window. Since the browser fires key events repeatedly while the user holds a key down, we could implement an "automatic release" of any keys that haven't had a recent "down" event. That would catch cases like this where we never got an explicit "up" event to end the movement.

@misslivirose
Copy link
Contributor Author

I like the idea of an automatic release - @emclaren hit this today and Blair mentioned still seeing it frequently

@misslivirose misslivirose added the P2 Address when able label Oct 14, 2019
@emclaren
Copy link
Contributor

emclaren commented Mar 9, 2020

I hit this bug often - I have also recently had an additional bug happen immediately following the controls getting stuck where everytime i click in the chatbox, a long video gets recorded. thus leading to lots of videos popping out about a few minutes later all at once. This has happened to me twice in the last week, but I cant quite figure out what leads to this (other than the controls getting stuck first).

@gfodor
Copy link
Contributor

gfodor commented Mar 9, 2020 via email

@misslivirose
Copy link
Contributor Author

I hit this a lot less often these days, but ran into this yesterday.

@misslivirose
Copy link
Contributor Author

There were three reports of this happening during XR Access

@emclaren
Copy link
Contributor

emclaren commented Aug 7, 2020

It was noted that one of the users this happened to at XR Access Symposium was using a screen reader and was unaware that this was happening because we have no feedback when users move.

related to this: #2701

@emclaren
Copy link
Contributor

emclaren commented Aug 9, 2020

This happened to me today because i accidentally pressed Command+S at the same time. Also noted that Command+A makes the controls get stuck as well.

@matthewbcool
Copy link
Contributor

unable to repro, closing for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug P2 Address when able
Projects
None yet
Development

No branches or pull requests

6 participants