Closed Bug 494360 Opened 16 years ago Closed 13 years ago

[@font-face] font family names should hide platform fonts, even when errors occur

Categories

(Core :: Graphics, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: jtd, Assigned: jfkthame)

References

()

Details

Attachments

(1 file, 1 obsolete file)

When an @font-face face fails to load for a font family that matches an existing platform font we load the platform font instead of falling back to the next font in the fallback list. For example: @font-face { font-family: Arial; src: url(font.ttf); } body { font-family: Arial, serif; } In this situation, text on the page should *never* display with Arial, it should either display with font.ttf or with a serif font. The testcase URL includes @font-face rules with intentionally bad URL's, so the text should appear using a serif face. The root of the problem here is that the user font set lookup only returns yes/no for whether a font is loaded. It should return not-found, found-loaded and found-not-yet-loaded. In the found-not-yet-loaded, the font lookup should skip the platform font lookup.
Attached patch reftests (obsolete) — Splinter Review
Reftests for testing this, with and without URL's that point at valid font data.
Summary: font family names should hide platform fonts, even when errors occur → [@font-face] font family names should hide platform fonts, even when errors occur
Why was I CCed to this bug here? Does this bug here have something to do with another bug?
I've been working on a patch for bug 623711 that should also fix this.
Assignee: jdaggett → jfkthame
Depends on: 623711
The primary bug here was fixed in bug 623711, but the original reftests didn't quite work as written; updated them so as to pass reliably. Note that bug 668758 also interacts with this issue (and is one reason for problems with the original tests here); that needs an additional patch and its own tests, but I'd like to go ahead and land these tests and resolve this bug.
Attachment #379080 - Attachment is obsolete: true
Attachment #543410 - Flags: review?(jdaggett)
Attachment #543410 - Flags: review?(jdaggett) → review+
Landed tests: http://hg.mozilla.org/mozilla-central/rev/7daa4cc9fb07 Marking this as Fixed now that we have tests in place (the actual code fix happened in bug 623711).
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: