Closed
Bug 1930643
Opened 1 year ago
Closed 1 year ago
Decide what to do with `alerts.showFavicons`
Categories
(Toolkit :: Alerts Service, task)
Toolkit
Alerts Service
Tracking
()
RESOLVED
FIXED
138 Branch
| Tracking | Status | |
|---|---|---|
| firefox138 | --- | fixed |
People
(Reporter: saschanaz, Assigned: saschanaz)
References
(Blocks 1 open bug)
Details
Attachments
(4 files)
This pref has been there since 2016 but always been disabled by default. Currently it's only implemented in XUL (via nsIAlertsIconURI) and macOS backend (via nsIAlertsIconData).
- Check if it still works
- Investigate whether it's possible to implement on other backends (probably not for Windows, maybe for libnotify)
| Assignee | ||
Comment 1•1 year ago
|
||
Updated•1 year ago
|
Assignee: nobody → krosylight
Status: NEW → ASSIGNED
| Assignee | ||
Comment 2•1 year ago
|
||
Note that this has nothing to do with Notification.icon even though the code mentions icon.
| Assignee | ||
Comment 3•1 year ago
|
||
| Assignee | ||
Comment 4•1 year ago
|
||
No other browser shows favicon on notifications, and even though the the latest macOS 15.3.2 passes the condition to enter the block, it does not make any actual visual change anymore.
Depends on D241434
Pushed by krosylight@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b9b608e3f5be
Part 1: Remove all warnings in nsAlertsService.cpp/h r=nalexander
https://hg.mozilla.org/integration/autoland/rev/998362f750db
Part 2: Remove favicon support from nsAlertsService r=nalexander
https://hg.mozilla.org/integration/autoland/rev/696af1aae0e9
Part 3: Remove icon support from XULAlerts r=nalexander
https://hg.mozilla.org/integration/autoland/rev/212cfcc12afa
Part 4: Remove icon support from OSXNotificationCenter r=nalexander
Comment 7•1 year ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/b9b608e3f5be
https://hg.mozilla.org/mozilla-central/rev/998362f750db
https://hg.mozilla.org/mozilla-central/rev/696af1aae0e9
https://hg.mozilla.org/mozilla-central/rev/212cfcc12afa
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox138:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 138 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•