Closed
Bug 1254300
Opened 8 years ago
Closed 6 years ago
Calling notifications.create always dismisses existing notifications
Categories
(WebExtensions :: Frontend, defect, P3)
WebExtensions
Frontend
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: wbamberg, Unassigned)
Details
(Whiteboard: [notifications]triaged)
Attachments
(1 file)
3.58 KB,
application/x-xpinstall
|
Details |
If you call chrome.notifications.create twice in succession, then: * if you pass an ID in the second call, and it matches the ID in the first call, then the first notification should be cleared. * otherwise, the first notification should not be cleared In Firefox, what I'm seeing is that the first notification is always cleared. I've attached a WebExtension demo.
Updated•8 years ago
|
Whiteboard: [notifications]
Updated•8 years ago
|
Priority: -- → P3
Whiteboard: [notifications] → [notifications]triaged
Comment 1•8 years ago
|
||
But there's not the same equivalent problem on Firefox sdk notifications when there's several notifications in a short time?
Updated•8 years ago
|
Component: WebExtensions: Untriaged → WebExtensions: Frontend
Comment 2•8 years ago
|
||
Just tested this in both current Beta and Nightly, and it WORKSFORME. Is this still an issue? Possibly scoped to OSX only?
Flags: needinfo?(wbamberg)
Comment 3•8 years ago
|
||
Forgot to mention: tested on Windows 7.
Comment 5•6 years ago
|
||
I just tested this. If I use the same id, I see that the notification is cleared in the osx notification center. If I use different id's, while I only see one notification bubble, the notification center shows me all the notifications (they are not cleared).
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•