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

Can't set focus inside debug complex hover tooltip #3293

Closed
stevencl opened this issue Feb 23, 2016 · 5 comments
Closed

Can't set focus inside debug complex hover tooltip #3293

stevencl opened this issue Feb 23, 2016 · 5 comments
Assignees
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster verified Verification succeeded

Comments

@stevencl
Copy link
Member

With accessibility mode on and tab set to move focus, I can't seem to use the keyboard to navigate to or inside the tooltip that appears when hovering over a complex object in the debugger.

Found while testing #3246

@stevencl stevencl added bug Issue identified by VS Code Team member as probable bug accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues labels Feb 23, 2016
@bpasero bpasero assigned isidorn and unassigned bpasero Feb 29, 2016
@isidorn isidorn added the info-needed Issue requires more information from poster label Feb 29, 2016
@isidorn
Copy link
Contributor

isidorn commented Feb 29, 2016

@stevencl did you try ctrl + k, ctrl + i. Can you move focus using the same keyboard shortuct to the regular, non debug hover? Can you move focus inside a simple debug hover?
This works fine for me on the mac

@isidorn isidorn assigned stevencl and unassigned isidorn Feb 29, 2016
@stevencl
Copy link
Member Author

stevencl commented Mar 9, 2016

I didn't use Ctrl K, Ctrl I originally, wasn't aware of that. After clicking inside the tooltip with the mouse then pressing Ctrl K, Ctrl I, I am able to move focus inside the tooltip.
But, I wonder how useful this will be? By requiring the user to use the mouse to reveal the hover and then click inside it, it seems like we are not fully enabling keyboard accessibility.
Perhaps though there is another keyboard shortcut that I am not aware of that brings up the tooltip for the symbol located next to the cursor?

@stevencl stevencl assigned isidorn and unassigned stevencl Mar 9, 2016
@isidorn
Copy link
Contributor

isidorn commented Mar 9, 2016

I think there is a misunderstanding, ctrl k cltr i is the keyboard shortcut that brings up the tooltip for the symbol located next to the cursor. You do not need to use the mouse at all!

This keybinding also works for regular hover - same way as visual studio is doing it.

If this does not work for you please reopen the bug.

@isidorn isidorn closed this as completed Mar 9, 2016
@stevencl
Copy link
Member Author

stevencl commented Mar 9, 2016

D'oh! I don't know why I didn't see this before.

@isidorn
Copy link
Contributor

isidorn commented Mar 9, 2016

No problemo, just glad we got the confusion out of the way 🐙

@isidorn isidorn assigned stevencl and unassigned isidorn Mar 10, 2016
@isidorn isidorn added the verified Verification succeeded label Mar 10, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
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 bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants