Calling notifications.create always dismisses existing notifications

NEW
Unassigned

Status

()

Toolkit
WebExtensions: Frontend
P3
normal
a year ago
5 months ago

People

(Reporter: wbamberg, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [notifications]triaged)

Attachments

(1 attachment)

(Reporter)

Description

a year ago
Created attachment 8727600 [details]
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]

Updated

a year ago
Priority: -- → P3
Whiteboard: [notifications] → [notifications]triaged

Comment 1

11 months ago
But there's not the same equivalent problem on Firefox sdk notifications when there's several notifications in a short time?

Updated

8 months ago
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.
(Reporter)

Comment 4

7 months ago
I still see this on OS X.
Flags: needinfo?(wbamberg)
You need to log in before you can comment on or make changes to this bug.