GDocs favicons no longer display in the tab strip
Categories
(Core :: DOM: Networking, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox106 | --- | unaffected |
firefox107 | --- | unaffected |
firefox108 | --- | disabled |
firefox109 | --- | verified |
firefox110 | --- | verified |
People
(Reporter: mconley, Assigned: sefeng)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [orb:m1], [wptsync upstream])
Attachments
(3 files)
STR:
- Visit this test document
- Look at the tab strip
ER:
The GDocs favicon should appear.
AR:
The GDocs favicon does not appear. When pinned, the default favicon appears instead.
Reporter | ||
Comment 1•2 years ago
|
||
ni?ing sefeng per your mailing list post. :)
Reporter | ||
Comment 2•2 years ago
|
||
(I identified the regression range using mozregression)
Updated•2 years ago
|
Comment 3•2 years ago
|
||
Set release status flags based on info from the regressing bug 1785331
Assignee | ||
Comment 4•2 years ago
|
||
Looks like our sniffer failed to identify the ico file was an image. This is Nightly only, so I am changing the status.
Comment 5•2 years ago
|
||
We can set the status to disabled once 108 goes to Beta, but for now 108 is affected.
Comment 6•2 years ago
|
||
In today's Nightly I see favicons for gdocs but not pinned gdocs or gmail (but it does work for pinned gcal).
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 7•2 years ago
|
||
Our current code uses PeekStream to get the data and pass them
over to the sniffer, however it doesn't count the case where the
contents are compressed, so the sniffer would fail to determine
the type of contents.
This patches introduces a sub class of nsHTTPCompressConv which
allows when the sniffer type is ORB, we'll decompresses the first
chunk of the data before making an ORB decision.
Updated•2 years ago
|
Updated•2 years ago
|
Assignee | ||
Comment 8•2 years ago
|
||
It seems that these stuff aren't really needed because whatever
reaches to here either successfully synthesized requests or requests
with system principal (ie: the requests we manually created in
test_synthesized_response.js).
If those conditions are true, then these ORB checks will have no
effect, so we can remove them.
Depends on D161167
Updated•2 years ago
|
Updated•2 years ago
|
Comment 11•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/5c12f99543e1
https://hg.mozilla.org/mozilla-central/rev/042e5a858d11
![]() |
||
Comment 12•2 years ago
|
||
Can we get this work uplifted to 108?
Assignee | ||
Comment 13•2 years ago
|
||
I don't think we need to since ORB has been turned off in bug 1798227, so 108 doesn't have it?
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Comment 17•2 years ago
|
||
I was able to reproduce the issue on Win10 using FF build 108.0a1(20221028212211).
Verified as fixed on Win10/Ubuntu 20.04 using builds 109.0b1(20221212143511) and 110.0a1(20221213165020).
Description
•