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

Empty tree should not be focusable #2347

Closed
alexdima opened this issue Jan 26, 2016 · 11 comments
Closed

Empty tree should not be focusable #2347

alexdima opened this issue Jan 26, 2016 · 11 comments
Assignees
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues ux User experience issues verified Verification succeeded
Milestone

Comments

@alexdima
Copy link
Member

Testing #2145

e.g. debug variables tree

image

@alexdima alexdima added bug Issue identified by VS Code Team member as probable bug accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues labels Jan 26, 2016
@bpasero
Copy link
Member

bpasero commented Jan 26, 2016

@alexandrudima an empty tree can still have a context menu associated. are you saying we should detect the case where the tree is empty && has no context menu? I am not sure this would confuse people why sometimes they see blue and sometimes they do not.

@alexdima
Copy link
Member Author

Good point about the context menu case, so maybe it makes sense to tab into an empty explorer tree given that's the only place where a context menu can be invoked.

IMHO in this case, tabbing into an empty variable list in the debugger is pretty useless.

@bpasero
Copy link
Member

bpasero commented Jan 26, 2016

@alexandrudima but that is up to the tree right? e.g. I can also tab into watch expressions to create a new one there.

@alexdima
Copy link
Member Author

Right clicking in empty spaces appears to be common:

  • e.g. in this webpage I can right click on the whitespace
  • e.g. on my desktop I can right click anywhere on it
  • however, the whitespace on this webpage is not "focusable" and there must be alternative ways to get those actions besides context menu...

@bpasero
Copy link
Member

bpasero commented Jan 26, 2016

@alexandrudima sorry can you clarify what your last comment means?

@alexdima
Copy link
Member Author

gif time :)

I can do a contextmenu with the mouse in areas where I cannot go to via tab focus. e.g. the whitespace on this webpage or the desktop. I only assume there must be alternative ways to trigger those actions since I cannot get to focus the whitespace to trigger a contextmenu with the keyboard

contextmenu-even-in-nonfocusable

@bpasero
Copy link
Member

bpasero commented Jan 26, 2016

Well yeah, might be. All I am saying is that imho it makes sense to draw the blue border in the tree as long as you can trigger the context menu (using the context menu key on the keyboard). Even if there are other ways I find this a nice gesture.

@bpasero bpasero modified the milestone: Jan 2016 Jan 26, 2016
@bpasero bpasero added the ux User experience issues label Jan 26, 2016
@bpasero bpasero modified the milestones: Feb 2016, Jan 2016 Jan 26, 2016
@bpasero bpasero removed the bug Issue identified by VS Code Team member as probable bug label Jan 28, 2016
@bpasero bpasero assigned stevencl and unassigned bpasero Jan 28, 2016
@bpasero
Copy link
Member

bpasero commented Jan 28, 2016

We should take this to UX meeting.

@stevencl
Copy link
Member

Even if there is no context menu available for a focusable UI panel I think we should still allow the user to tab into it to set focus. This lets them know and discover the different UI panels and components. For example, a screen reader might read out something about the empty panel.

@bpasero
Copy link
Member

bpasero commented Jan 29, 2016

Yeah, also a good point. In fact every tree has a meaningful aria label assigned now.

@bpasero
Copy link
Member

bpasero commented Feb 5, 2016

Closing.

@bpasero bpasero closed this as completed Feb 5, 2016
@stevencl stevencl added the verified Verification succeeded label Feb 26, 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 ux User experience issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants