Closed
Bug 1174299
Opened 9 years ago
Closed 9 years ago
Chrome selective-caching demo does not render fonts correctly in Firefox
Categories
(Core :: DOM: Service Workers, defect)
Core
DOM: Service Workers
Tracking
()
RESOLVED
DUPLICATE
of bug 1167808
People
(Reporter: u279076, Unassigned)
Details
Attachments
(1 file)
|
(deleted),
image/png
|
Details |
Screenshot from 2015-06-12 13-30-00.png
Steps
1. Load https://googlechrome.github.io/samples/service-worker/selective-caching/index.html
> Notice the font renders "funky" in Firefox and Chrome
2. Reload the page
> Notice the font renders "funky" in Chrome but "normally" in Firefox
The attached screenshot illustrates this bug (left is Firefox, right is Chrome)
|
||
Updated•9 years ago
|
Blocks: ServiceWorkers-v1
|
|
||
Comment 1•9 years ago
|
||
This might also be an instance of the opaque response handling issue in bug 1167808. The long delay with the spinning tab icon is what suggests its the case. We would need to look to see if the font is cross-origin, though.
|
|
||
Comment 2•9 years ago
|
||
Ah, yea. Its coming from fonts.gstatic.com. So I believe its another case of an opaque response body being ignored.
No longer blocks: ServiceWorkers-v1
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•