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

Voice Over in terminal gets into focus loop when holding arrow #42561

Closed
mjbvz opened this issue Jan 30, 2018 · 6 comments
Closed

Voice Over in terminal gets into focus loop when holding arrow #42561

mjbvz opened this issue Jan 30, 2018 · 6 comments
Assignees
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues *as-designed Described behavior is as designed info-needed Issue requires more information from poster terminal General terminal issues that don't fall under another label

Comments

@mjbvz
Copy link
Collaborator

mjbvz commented Jan 30, 2018

#42278

Issue Type

Bug

Description

  1. Enable voice over
  2. In terminal
  3. Get a few screens of output
  4. Hold VO+left arrow to scroll through it

Expected
This scrolls through lines and continues when you hit top of the screen

Actual
Once we hit the top of the screen, the focus seems to go into a loop:

jan-30-2018 14-32-05

When pressing the arrow key one at a time instead of holding it down, everything works as expected

VS Code Info

VS Code version: Code - Insiders 1.20.0-insider (8cac1ac, 2018-01-30T17:19:56.812Z)
OS version: Darwin x64 17.3.0

System Info
Item Value
CPUs Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz (8 x 2200)
Load (avg) 3, 4, 4
Memory (System) 16.00GB (0.83GB free)
Process Argv /Applications/Visual Studio Code - Insiders.app/Contents/MacOS/Electron
Screen Reader yes
VM 0%
Reproduces without extensions
@mjbvz mjbvz added the accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues label Jan 30, 2018
@Tyriar
Copy link
Member

Tyriar commented Jan 31, 2018

@mjbvz to clarify, it didn't "trap" the focus after this happened when you pressed either up or down did it?

@Tyriar Tyriar added info-needed Issue requires more information from poster terminal General terminal issues that don't fall under another label labels Jan 31, 2018
@vscodebot vscodebot bot closed this as completed Feb 7, 2018
@vscodebot
Copy link

vscodebot bot commented Feb 7, 2018

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

@mjbvz
Copy link
Collaborator Author

mjbvz commented Feb 7, 2018

@Tyriar No, not for single presses. This only happened when holding the key down to select through multiple elements

@mjbvz mjbvz reopened this Feb 7, 2018
@mjbvz mjbvz added info-needed Issue requires more information from poster and removed info-needed Issue requires more information from poster labels Feb 7, 2018
@Tyriar
Copy link
Member

Tyriar commented Feb 8, 2018

@mjbvz but if you stop and press the other direction does everything go back to normal or did it get into a corrupted state? If the former then this is as good as we can do AFAIK.

@Tyriar Tyriar added info-needed Issue requires more information from poster and removed info-needed Issue requires more information from poster labels Feb 8, 2018
@mjbvz
Copy link
Collaborator Author

mjbvz commented Feb 8, 2018

Yes, if you stop everything is normal afterwards

@Tyriar
Copy link
Member

Tyriar commented Feb 8, 2018

Closing then as I couldn't see a way we could fix this, plus it's not disastrous if it happens, the user can just backtrack

@Tyriar Tyriar closed this as completed Feb 8, 2018
@Tyriar Tyriar added the *as-designed Described behavior is as designed label Feb 8, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues *as-designed Described behavior is as designed info-needed Issue requires more information from poster terminal General terminal issues that don't fall under another label
Projects
None yet
Development

No branches or pull requests

2 participants