Closed Bug 1254300 Opened 8 years ago Closed 6 years ago

Calling notifications.create always dismisses existing notifications

Categories

(WebExtensions :: Frontend, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: wbamberg, Unassigned)

Details

(Whiteboard: [notifications]triaged)

Attachments

(1 file)

Attached file notify-bug.xpi
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.
Whiteboard: [notifications]
Priority: -- → P3
Whiteboard: [notifications] → [notifications]triaged
But there's not the same equivalent problem on Firefox sdk notifications when there's several notifications in a short time?
Component: WebExtensions: Untriaged → WebExtensions: Frontend
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)
Forgot to mention: tested on Windows 7.
I still see this on OS X.
Flags: needinfo?(wbamberg)
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
Product: Toolkit → WebExtensions
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: