Closed
Bug 1878383
Opened 2 years ago
Closed 1 month ago
onnotificationclose is not implemented on Android
Categories
(Core :: DOM: Notifications, defect, P3)
Core
DOM: Notifications
Tracking
()
RESOLVED
FIXED
142 Branch
Tracking | Status | |
---|---|---|
firefox142 | --- | fixed |
People
(Reporter: saschanaz, Assigned: saschanaz)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
While looking at bug 1875257 I found Android somehow fails to fire onnotificationclose in certain situation, it needs some investigation.
Updated•2 years ago
|
Severity: -- → S3
Priority: -- → P3
Assignee | ||
Updated•1 year ago
|
Component: DOM: Push Subscriptions → DOM: Notifications
Assignee | ||
Updated•1 month ago
|
Summary: onnotificationclose is unstable on Android → onnotificationclose is not implemented on Android
Assignee | ||
Comment 1•1 month ago
|
||
I had a wrong assumption in D248312 that alertfinished will always be called by GeckoView, but turns out that each backend calls it immediately within CloseAlert implementation.
This aligns Android implementation with others, and bug 1975432 is filed for deduplication.
Pushed by krosylight@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/979ebda30b4a
https://hg.mozilla.org/integration/autoland/rev/d7bcf597a702
Fire alertfinished in AndroidAlerts::CloseAlert r=emilio,geckoview-reviewers,owlish
Comment 3•1 month ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 1 month ago
status-firefox142:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 142 Branch
Updated•21 days ago
|
QA Whiteboard: [qa-triage-done-c143/b142]
You need to log in
before you can comment on or make changes to this bug.
Description
•