-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Display "trusted" and "untrusted" notifications #1658
Conversation
gnestor
commented
Aug 4, 2016
Related #1293 |
@ellisonbg Can you UX test? |
Nice! |
I would just not use the One of the reasons I think it would be better, is that I don't want this action to become something which is click-through like the UAC on windows. Otherwise +1 |
Ok, I just switched to classic style. One other question: Should the "Trusted" notification hide itself after a second or so? Currently both notifications are persisted. If the "Untrusted" notification is clicked, the user is prompted to trust the notebook. If the "Trusted" notification is clicked, the notification hides. |
I think that's a good compromise. And it's easy enough to change afterward if needed. As @Phyks was the first initiator of that, we can ask him his thoughts. |
I think I'd be inclined to hide both notifications after 10 seconds or so, to reduce the likelihood that the user will click to make it go away. Even in blue, it still stands out quite a bit. |
Both are gray now. IIUC. |
Sorry, I did not have much time to follow it and eventually work on my PR lately. Thanks @gnestor ! Your design implementation looks really cool! I would not be in favor of hiding the untrusted notification, as the user may not notice it before it goes away and the main purpose of this feature was to have an indication that a notebook is untrusted. The trusted notification can go away though I think, as it results from either a user interaction, or a notebook being safe from the loading. |
Ok, @minrk should we switch this to 5.0 before merging or leave it at 4.3 and backport? |
You can leave at 4.3 for the backport script to find the issue. |
That's what I was thinking... |
Yeah ! |