Closed
Bug 1916687
Opened 2 months ago
Closed 2 months ago
favicons should be upgraded as mixed content
Categories
(Core :: DOM: Security, enhancement, P3)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
132 Branch
People
(Reporter: freddy, Assigned: freddy)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file)
No description provided.
|
Assignee | |
Comment 1•2 months ago
|
||
|
||
Updated•2 months ago
|
Attachment #9422535 -
Attachment description: WIP: Bug 1916687 - update favicon as mixed content → Bug 1916687 - update favicon as mixed content r?pbz,tschuster
Pushed by fbraun@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/93512fd15d81
update favicon as mixed content r=tschuster,mak
|
||
Comment 3•2 months ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
status-firefox132:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 132 Branch
|
|
Assignee | |
Comment 4•2 months ago
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]: This changes how some web pages will look like. However, it would align Firefox with other browsers (at least Chrome)
[Affects Firefox for Android]: Yes.
[Suggested wording]: As a follow-up to our work to upgrade mixed content starting Firefox 127, we will now also block HTTP-favicons if they can not be received over HTTPS instead.
[Links (documentation, blog post, etc)]: https://blog.mozilla.org/security/2024/06/05/firefox-will-upgrade-more-mixed-content-in-version-127/
relnote-firefox:
--- → ?
|
||
Updated•2 months ago
|
Flags: qe-verify+
You need to log in
before you can comment on or make changes to this bug.
Description
•