Closed
Bug 1582875
Opened 6 years ago
Closed 6 years ago
Reason for font fallback
Categories
(DevTools :: Inspector, enhancement)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1456844
People
(Reporter: james.a.rosen, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
- Specify a valid @font-face that refers to a URL that has some problem. (See What should have happened, below, for more info.)
- Use that font-face in an element on the page with at least one other font-face as fallback
- Inspect the element
Actual results:
I can see that the fallback is selected (see also #1429761), but not why.
Expected results:
I'd like to know what caused Firefox to select the fallback font. I can think of four possible reasons:
- (a) it could point to a URL that returns a 4xx or 5xx error
- (b) the response could fail to include proper CORS headers
- (c) the server could take too long to respond and the
@font-face
declaration includesfont-display: fallback
- (d) the file returned could be not a font file
Comment 1•6 years ago
|
||
Hi James,
Thanks for filing this!
There is another bug open for this feature request: bug 1456844.
I have copied over the new information from this bug to the other one and I will close this one as a duplicate. Please add more context to that bug if you feel it is necessary.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•4 years ago
|
Component: Inspector: Fonts → Inspector
You need to log in
before you can comment on or make changes to this bug.
Description
•