-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
unread-anywhere - Add button
#8638
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
Conversation
|
To me, that style looks like a broken button (or a missing icon). I'll disable the feature anyway (because I have too many unread notifications for it to be useful), so I don't care enough to open an issue about it. |
|
I don't plan on using this feature, because to me, keeping unread notifications unread is an important part of making sure I read them at the right time, and I have a mix of personal and professional notifications, so I never want to mix them. There was a suggestion on making it on alt+click that was set aside as "too hard to discover to be useful". What about changing the tooltip of the button to "You have unread notifications. Use alt+click to open them all" That said, I've disabled the feature. I think it's the first time I had to do that, and I'm perfectly fine doing that, but I wanted to offer some feedback so that there's a chance to revisit design choices. But, again, I'm perfectly fine if nothing changes. |
|
Thanks for the feedback! Keep them coming. This is the reasoning:
This is the closest I could get:
Improvements are still possible, so I'm open to suggestions. For example:
|
there is ?! I never saw it ! (I'm seeing it now) |
|
See #8642 |




unread-anywhere- Add button #8619The notification buttons is a rather vital part of GitHub so changes here need to be careful.
I thought about using a larger blue bubble but that is both visually distracting and not really clickable (it's
::before, which you can't detect in aclickevent)This style was one of the ones initially suggested.
Also I left it visible even if there are no notifications, because GitHub's UI is not necessarily up to date (#1426)
Screenshot