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

[0.10.7] Pane highlight outline #2661

Closed
SamVerschueren opened this issue Feb 3, 2016 · 13 comments
Closed

[0.10.7] Pane highlight outline #2661

SamVerschueren opened this issue Feb 3, 2016 · 13 comments
Assignees
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues ux User experience issues

Comments

@SamVerschueren
Copy link
Contributor

Since the insider build, it looks like the panes can be highlighted when clicked. It really looks weird to me and doesn't have added value (but maybe there is). Is this a bug or not?

screen shot 2016-02-03 at 09 33 04
screen shot 2016-02-03 at 09 33 15

@bpasero bpasero added ux User experience issues accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues labels Feb 3, 2016
@bpasero bpasero assigned stevencl and unassigned bpasero Feb 3, 2016
@bpasero
Copy link
Member

bpasero commented Feb 3, 2016

@SamVerschueren this is part of our ongoing work to be more accessible: #2108

Indicating the currently focused element is a requirement to be accessible. You can see this in action when tabbing around the UI with the tab key.

As to wether the affordance we show is good or bad, I assign this to UX for discussion.

@bpasero
Copy link
Member

bpasero commented Feb 3, 2016

The added value is Accessibility :]

@SamVerschueren
Copy link
Contributor Author

Aha, makes sense :). Would it be possible to make it an option (which is default on) to turn this behaviour off?

@bpasero
Copy link
Member

bpasero commented Feb 3, 2016

Yeap maybe. For now I like that everyone sees it and can report feedback on it.

@SamVerschueren
Copy link
Contributor Author

👍

@SamVerschueren
Copy link
Contributor Author

Might be more difficult. I like the highlighting when navigating with tabs. It's very clear what item is selected. But when I start debugging something, the the highlighted pane is automatically switched 3 times in a very short timespan which makes it very weird. Think we should just get the discussion going on how we can improve these things.

@bpasero
Copy link
Member

bpasero commented Feb 3, 2016

@SamVerschueren can you capture from where to where it moves?

@SamVerschueren
Copy link
Contributor Author

I thought I saw it when debugging, but it seems that it occurs when running my vscode-yo plugin.

debug

@bpasero
Copy link
Member

bpasero commented Feb 3, 2016

@SamVerschueren I see, the issue is that the picker closes, focus moves back to where it was and then back into the picker.

The blue line that you see for output is not a focus indicator actually, so you might get confused there easily.

@bpasero
Copy link
Member

bpasero commented Feb 3, 2016

It also only happens if no file is open because with a opened file, focus moves back to the file when quick picker closes.

@SamVerschueren
Copy link
Contributor Author

The blue line that you see for output is not a focus indicator actually, so you might get confused there easily.

Oh I see, you're right. The output panel never gets focus, although you get the idea that it receives focus because it switches so quickly.

It also only happens if no file is open because with a opened file, focus moves back to the file when quick picker closes.

Confirmed

But it just looks weird. Maybe I have to get used to it :).

@bpasero
Copy link
Member

bpasero commented Feb 5, 2016

Some things pushed and thoughts:

  • closing quick open no longer restores focus to the viewlet if no editor is open
  • we think about not coloring the output panel in blue but in a less strong color that does not interfere with focus
  • I went over many places in the tree where we quickly removed focus from the tree which results in the large blue border and relaxed that so that it does not happen that often anymore

I am closing this one and would like to hear more feedback.

@bpasero bpasero closed this as completed Feb 5, 2016
@SamVerschueren
Copy link
Contributor Author

Thanks! Will post some feedback if it gets released.

@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
Projects
None yet
Development

No branches or pull requests

3 participants