Closed
Bug 1218898
Opened 9 years ago
Closed 9 years ago
Notification is not dismissed when "closeNotification" button is clicked
Categories
(Core :: DOM: Push Subscriptions, defect)
Tracking
()
VERIFIED
FIXED
Tracking | Status | |
---|---|---|
firefox44 | --- | affected |
People
(Reporter: poiegas, Unassigned)
References
()
Details
Reproducible with: 44.0a1 (from 2015-10-26 and 2015-10-27)
Affected platform: Mac OS X 10.8
Steps to reproduce:
1. Navigate to "https://pdehaan.github.io/push-notification-test/" page.
2. Click on the "pop Notification" button and select "Always Receive Notifications" from doorhanger.
3. After notification is displayed, click on "closeNotification" button.
4. Observe the notification behavior.
Expected results:
Notification is immediately dismissed.
Actual results:
Notification persists until automatically closed after a period of time.
Comment 1•9 years ago
|
||
I'm not able to reproduce on mac 10.11. Can you test on Fx43 (Aurora) this will let us know if it's a change in behavior.
Reporter | ||
Comment 2•9 years ago
|
||
Hi Edwin. Verified this behavior on multiple Mac OS'es (10.6 to 10.11) and it only reproduces on Mac OS 10.8 on 44.0a1 Nightly build as mentioned in bug description.
Tested this also on Fx43 (Aurora) as you requested on the same Mac OS 10.8 and it does not reproduces.
Comment 3•9 years ago
|
||
Mozilla/5.0 (X11; Linux i686; rv:44.0) Gecko/20100101 Firefox/44.0
The issue is also reproducible on the latest Aurora using Ubuntu 14.04.
Updated•9 years ago
|
Comment 5•9 years ago
|
||
Hi Paul and Brindusa! I think this should be fixed in Firefox 46: bug 1220337 for OS X and bug 1219855 for Ubuntu. Please reopen if it's still an issue.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 6•1 year ago
|
||
Clean-up time on old issues. Marking this one as verified since it does not reproduce on the latest builds using macOS 13.x, and since no one else complained about it reproducing since it has been fixed.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•