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

set default duration for messages in the left sidebar status bar #162

Closed
redshiftzero opened this issue Nov 12, 2018 · 2 comments
Closed

Comments

@redshiftzero
Copy link
Contributor

Description

In the status bar at the bottom of the application, the status bar messages have a default duration.

We should implement this for the status bar at the left sidebar of the application:

screen shot 2018-11-11 at 4 51 57 pm

@redshiftzero redshiftzero added this to the 0.1.0beta milestone Nov 12, 2018
@ninavizz
Copy link
Member

In the way @ntoll has the QT app setup right now, are these messages placeholders for what will eventually be experienced by users as transient (or, "toast") notifications (my interpretation from the above screenshot)?

Goal in asking this: is the longer-term interest to establish a default auto-expire timing for transient/toast notifications?

Transient/toast notifications should display for 5 seconds at 100% alpha, then fade-out to 0% over 2 seconds. The fading-bit, If possible. If not, then just 5 seconds should be the default. Longer messages will require more time, but no message should display for fewer than 4 or 5 seconds.

4 seconds is what Google recommends in their Material design spec, and other articles I've read cite 5.

@eloquence eloquence modified the milestones: 0.2.0beta, 0.2.0alpha Jul 2, 2019
@eloquence eloquence removed this from the 0.2.0alpha milestone Dec 12, 2019
@eloquence
Copy link
Member

I'm assuming this can be closed since we now have a single status bar at the top which does appear to consistently go away after a few seconds; please reopen if this is still relevant.

legoktm pushed a commit that referenced this issue Dec 15, 2023
use latest pip-tools (see securedrop-debian-packaging#248)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants