Closed
Bug 1211721
Opened 9 years ago
Closed 9 years ago
Set the duration of a notification display to a reasonable amount for interaction when requireInteraction=false
Categories
(Toolkit Graveyard :: Notifications and Alerts, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1201397
People
(Reporter: edwong, Unassigned)
Details
This is for Windows and Linux and Mac Notification center control's it's display time. Currently, display time is 3-4 sec. Shall we entertain a time of 10s - 3600s? If you walk away from you laptop, you still may want to interact with it.
Comment 1•9 years ago
|
||
(In reply to Edwin Wong [:edwong] from comment #0) > This is for Windows and Linux and Mac Notification center control's it's > display time. Currently, display time is 3-4 sec. Shall we entertain a time > of 10s - 3600s? I think we would probably only change this for XUL notifications where we have chosen our own arbitrary number. When talking with a11y folks in Toronto last week, they suggested 6 - 12 seconds but as a separate bug it needs to not auto-hide if keyboard focus is moving inside of it (like we do for mouse hover). > If you walk away from you laptop, you still may want to interact with it. We should just be smarter about that case in a separate bug. I don't think we should pick the default value to try and solve that problem too.
Reporter | ||
Comment 2•9 years ago
|
||
* maybe we can create a pref for the display duration so that we can change it in a dot release. * It's important to understand the use cases here. If I'm working and I see a notification, I want to be able to read it but I also want it to go away so I'm not interrupted. I really want both time to read and go away. * bmaggs to propose duration.
Flags: needinfo?(wmaggs)
Comment 3•9 years ago
|
||
We decided to go with 12 seconds as the duration. This change is being made in bug 1201397.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(wmaggs)
Resolution: --- → DUPLICATE
Updated•1 year ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•