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

Notifications UX #1135

Closed
stevencl opened this issue Dec 9, 2015 · 3 comments
Closed

Notifications UX #1135

stevencl opened this issue Dec 9, 2015 · 3 comments
Assignees
Labels
ux User experience issues workbench-notifications Notification widget issues
Milestone

Comments

@stevencl
Copy link
Member

stevencl commented Dec 9, 2015

We need to explore improving the way that we display warnings, errors and notifications to users. Currently we have a variety of mechanisms (info in status bar, details in quick open, error/warning dialog).

We need a consistent way that prompts the user when there are notifications/errors/warnings for them to pay attention to and a consistent affordance for the user to get a holistic view of all of the notitications/errors/warnings.

@stevencl stevencl added the UX label Dec 9, 2015
@stevencl stevencl self-assigned this Dec 9, 2015
@stevencl stevencl added ux User experience issues and removed UX labels Dec 9, 2015
@egamma egamma modified the milestone: Backlog Dec 10, 2015
@Alphapage
Copy link

I'm agree with you.
It would be great to have a notifications center.

For extensions, status bar messages is the only way to display info for a short time without disturbing the user too much, but it is difficult to attract the attention.
The only way is to show a warning|info|error message, but the user must interact with it which is not necessary in most cases. So, a notification center would be a great enhancement to track non blocking messages (displayed for 5 seconds only by default for example).

@schittli
Copy link

schittli commented Feb 1, 2018

We really cannot believe you introduced this kind of annoying feature, especially because every other IDE has solved this kind of message-handling years ago in a perfect way: the usual solution does not annoy users and nobody reclaims that they are missing notification.

Therefore, it's really strange that you need more than 2 years to roll it back and reapply the old and great working concept.

@bpasero
Copy link
Member

bpasero commented Feb 10, 2018

Duplicate of #22388

@bpasero bpasero marked this as a duplicate of #22388 Feb 10, 2018
@bpasero bpasero closed this as completed Feb 10, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
ux User experience issues workbench-notifications Notification widget issues
Projects
None yet
Development

No branches or pull requests

5 participants