Closed
Bug 1810709
Opened 1 year ago
Closed 1 year ago
Unreliable evaluation of the "first available font" for CSS purposes
Categories
(Core :: Layout: Text and Fonts, defect)
Core
Layout: Text and Fonts
Tracking
()
RESOLVED
FIXED
111 Branch
Tracking | Status | |
---|---|---|
firefox111 | --- | fixed |
People
(Reporter: jfkthame, Assigned: jfkthame)
Details
Attachments
(1 file)
The CSS Fonts spec defines the first available font, to be used in computing things like font-relative lengths and 'normal' line-height. This almost corresponds to Gecko's gfxFontGroup::GetFirstValidFont
method, but our implementation is not quite correct.
In particular, GetFirstValidFont will return the first font in the fontGroup's list, if it has been instantiated already, even if that font excludes the <space> character. This is incorrect, and results in some WPT test failures.
Assignee | ||
Comment 1•1 year ago
|
||
Except in the case of <space>, which is not required to be present for the font to be used
as the "first available font" in CSS (https://drafts.csswg.org/css-fonts-4/#first-available-font);
for that, only unicode-range coverage is applicable.
Updated•1 year ago
|
Assignee: nobody → jfkthame
Status: NEW → ASSIGNED
Pushed by jkew@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/35a64e1c9e32 Make GetFirstValidFont() check whether the required character is supported by the font. r=emilio
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/38033 for changes under testing/web-platform/tests
Comment 4•1 year ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox111:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
Upstream PR merged by moz-wptsync-bot
You need to log in
before you can comment on or make changes to this bug.
Description
•