Closed
Bug 859207
Opened 12 years ago
Closed 10 years ago
[Statusbar] cannot remove App Update Notification by either clearing or swiping away.
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: hanj.kim25, Unassigned)
Details
(Whiteboard: [TD-8917])
1. Title : [Statusbar] cannot remove App Update Notification by either clearing or swiping away.
2. Precondition : Have an app update notification on statusbar.
3. Tester's Action : Try 'Clear all' button and swiping away.
4. Detailed Symptom (ENG.) : Nothing happens to the update notifications.
5. Expected : The update notification should disappear by clearing or swiping.
6. Reproducibility: Y
1)Frequency Rate : 100%
Updated•12 years ago
|
Blocks: b2g-app-updates
Comment 2•12 years ago
|
||
That's normal, that's how it works since the start.
That's a compromise we made because for app update we need more complex notifications, and therefore we don't use the normal notification system.
The same happens for app install notifications.
We could probably use some code to make them disappear as well, but I think that was part of the UX design to not make them disappear.
Flags: needinfo?(felash)
Comment 3•12 years ago
|
||
Hmm...okay. Josh - Can you add more input here from a UX perspective?
Flags: needinfo?(jcarpenter)
Comment 4•12 years ago
|
||
Hi Jason, for v1 this is known, due to wanting to push system updates aggressively. We don't love it, and are open to revisiting the decision, but it's not a priority given other issues that need to be dealt with first.
Flags: needinfo?(jcarpenter)
Updated•12 years ago
|
Updated•12 years ago
|
No longer blocks: b2g-apps-v1-next
Comment 5•10 years ago
|
||
seeing as this is not a bug according to the comments i will close this as invalid. If it still applies to the current builds and you see it fit to please feel free to open a feature request.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•