Open
Bug 952930
Opened 11 years ago
Updated 2 years ago
[UX] Design Spike: Have a coherent system for browser-level notifications
Categories
(Firefox :: General, defect)
Firefox
General
Tracking
()
NEW
People
(Reporter: ntim, Unassigned)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [Australis:P-])
App notifications such as "Sync failed" or "Firefox seems slow" should use doorhanger notifications instead of classic bar notifications as shown in those mockups :
http://people.mozilla.org/~shorlander/files/appWide-notifications-i01/appWide-notifications-i01.html
Reporter | ||
Updated•11 years ago
|
Reporter | ||
Updated•11 years ago
|
Whiteboard: [Australis:P4]
Comment 1•11 years ago
|
||
I don't think we should do this for the Australis v1. Much too big scope-wise, and not critical because not a regression.
Whiteboard: [Australis:P4] → [Australis:P-]
Reporter | ||
Updated•11 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•11 years ago
|
Flags: firefox-backlog+
Comment 2•11 years ago
|
||
I wouldn't call this an "Australis" bug at all, tbh. It builds on Australis, but so does everything we do in the future.
Also - I'm going to re-purpose this one to be about looking again at how we do browser-level notifications.
Summary: Australis - Implement new app notifications → [UX] Have a coherent system for browser-level notifications
Updated•11 years ago
|
Whiteboard: [Australis:P-] → [Australis:P-] p=13
Updated•10 years ago
|
Summary: [UX] Have a coherent system for browser-level notifications → [UX] Design Spike: Have a coherent system for browser-level notifications
Updated•10 years ago
|
Points: --- → 13
Whiteboard: [Australis:P-] p=13 → [Australis:P-]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•