[text-box-trim] Fix font baseline selection for `text` edge
Categories
(Core :: Layout: Block and Inline, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox154 | --- | fixed |
People
(Reporter: sajidanwar, Assigned: sajidanwar)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
See Bug 2050141 (and specifically, Sebastian's comment, my comment, and the attached test case). The text edge is supposed to use the text-over and text-under baselines, which in Firefox and other browsers is based on the max ascent and descent of the inline box's font. But my implementation instead selected the "trimmed" ascent and descent (ref), which additionally subtract the "internal leading" of the font (if any). This makes Firefox trim too far on certain fonts as can be seen in the test case on the other bug.
| Assignee | ||
Comment 1•1 month ago
|
||
Comment 4•1 month ago
|
||
Backed out for causing wpt failures at text-box-trim/text-box-trim-multicol-013.html
Backout Link
Push with failures
Failure Log
Failure line TEST-UNEXPECTED-FAIL | /css/css-inline/text-box-trim/text-box-trim-multicol-013.html | .multicol 1 - assert_equals:
| Assignee | ||
Comment 5•1 month ago
|
||
Test failed because it was checking the layout values before the Ahem font loaded. On Linux it seems the initial font family has internal leading, so fixing the trim baseline revealed this font loading issue. Updating the patch to fix the test case.
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/61354 for changes under testing/web-platform/tests
Comment 8•1 month ago
|
||
| bugherder | ||
Upstream PR was closed without merging
Updated•29 days ago
|
Upstream PR merged by moz-wptsync-bot
Description
•