You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an upcoming event notification "The event starts in 3 minutes" appears, it stays there until clicked or dismissed. A few minutes may have passed and the text will remain. It is easy to "finish one last thing" and lose track of time. If you don't touch the notification, you might still think you have time before the meeting starts, even though it has started 5 minutes ago. If the text could somehow be updated in real time, it would keep you aware of the actual time left.
Solution description
It would progressively show:
The event starts in 3 minutes
The event starts in 2 minutes
The event starts in 1 minute
The event is starting
The event has started 1 minute ago
...
I would expect a configuration option to disable this behavior and another one to have a limit before the notification is automatically dismissed.
Alternatives considered
Not sure.
Additional context
I was previously using Meeter that was doing this.
The text was updated successfully, but these errors were encountered:
Issue that this suggestion fixes
When an upcoming event notification "The event starts in 3 minutes" appears, it stays there until clicked or dismissed. A few minutes may have passed and the text will remain. It is easy to "finish one last thing" and lose track of time. If you don't touch the notification, you might still think you have time before the meeting starts, even though it has started 5 minutes ago. If the text could somehow be updated in real time, it would keep you aware of the actual time left.
Solution description
It would progressively show:
I would expect a configuration option to disable this behavior and another one to have a limit before the notification is automatically dismissed.
Alternatives considered
Not sure.
Additional context
I was previously using Meeter that was doing this.
The text was updated successfully, but these errors were encountered: