Closed
Bug 2008986
Opened 8 months ago
Closed 8 months ago
Automatically update the favicon moz-remote-image: URL when the color scheme changes
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
RESOLVED
FIXED
149 Branch
People
(Reporter: tschuster, Assigned: tschuster)
References
Details
(Keywords: sec-other, Whiteboard: [adv-main149-])
Attachments
(2 files)
SVG favicons can react to the chrome's theme/color-scheme using media queries. This means we have to update the image we load via moz-remote-image: when the dark/light state changes. (Similarly probably want to do this for the device pixel ratio as well?)
|
Assignee | |
Updated•8 months ago
|
Group: firefox-core-security
|
|
Assignee | |
Comment 1•8 months ago
|
||
|
|
Assignee | |
Comment 2•8 months ago
|
||
|
||
Updated•8 months ago
|
Type: task → defect
OS: Unspecified → All
Hardware: Unspecified → Desktop
Pushed by tschuster@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/b8ddaae9f7db
https://hg.mozilla.org/integration/autoland/rev/219990373617
Automatically update the favicon moz-remote-image: URL when the color scheme changes r=tabbrowser-reviewers,dao
https://github.com/mozilla-firefox/firefox/commit/dfee6299d7b6
https://hg.mozilla.org/integration/autoland/rev/024887c68256
Test automatic color-scheme changes in SVG favicons r=tabbrowser-reviewers,dao
|
||
Comment 4•8 months ago
|
||
https://hg-edge.mozilla.org/mozilla-central/rev/219990373617
https://hg-edge.mozilla.org/mozilla-central/rev/024887c68256
Group: firefox-core-security → core-security-release
Status: NEW → RESOLVED
Closed: 8 months ago
status-firefox147:
--- → wontfix
status-firefox148:
--- → wontfix
status-firefox149:
--- → fixed
status-firefox-esr115:
--- → wontfix
status-firefox-esr140:
--- → wontfix
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → 149 Branch
|
||
Updated•6 months ago
|
QA Whiteboard: [sec] [qa-triage-done-c150/b149]
|
||
Updated•6 months ago
|
Whiteboard: [adv-main149-]
|
||
Updated•1 month ago
|
Group: core-security-release
You need to log in
before you can comment on or make changes to this bug.
Description
•