Bottom of text in UI slightly cut
Categories
(Core :: Graphics: Text, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr140 | --- | unaffected |
| firefox-esr153 | --- | unaffected |
| firefox155 | --- | wontfix |
| firefox156 | --- | wontfix |
| firefox157 | --- | fixed |
People
(Reporter: mercichao, Assigned: gw)
References
(Regression)
Details
(Keywords: nightly-community, regression)
Attachments
(2 files)
The bottom of text in certain UI elements is slightly cut off. For example, in the bookmarks toolbar and the hamburger menu, the descenders of letters such as “g” are clipped.
Updated•4 days ago
|
Comment 1•4 days ago
•
|
||
Regression window:
https://hg-edge.mozilla.org/integration/autoland/pushloghtml?fromchange=e1737460dd209523c9591509f1c244f6eb6d59f9&tochange=79a3125a8baae1d42cc2b98eedb448472eb3bc42
Disable HWA fix the issue on Windows11.
Updated•4 days ago
|
Comment 2•4 days ago
|
||
Set release status flags based on info from the regressing bug 2050692
:gw, since you are the author of the regressor, bug 2050692, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 3•4 days ago
|
||
A glyph pen is sub-pixel positioned on one axis and rounded to a whole device
pixel on the other. Bug 2050692 left the clip exact on both, but that is only
needed on the sub-pixel axis: elsewhere an exact clip disagrees with the grid the
glyphs landed on, and since the shader clamps the glyph quad with no coverage
term, a clip edge falling mid-row drops that row of ink outright.
Nearest is the rounding that works: the line box is ascent + descent, so the clip
and the pen are both round(box offset + an integer) and stay flush at every
phase. Bug 2055145 rounded outward instead, which spills a pixel whenever the ink
does not round up (bug 2065629).
So derive the axes from the font's SubpixelDirection, mirroring the snap_bias
table it already drives; local-raster runs snap in raster space, so leave them.
The snap is applied in request_resources and stored on the run's scratch, so
culling still sees the unsnapped clip.
Exact and nearest differ only at the .5 tie, which is where the reftest puts it.
Updated•4 days ago
|
| Assignee | ||
Updated•4 days ago
|
Updated•3 days ago
|
Comment 5•3 days ago
|
||
| bugherder | ||
Comment 6•3 days ago
|
||
The patch landed in nightly and beta is affected.
:gw, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
- If no, please set
status-firefox156towontfix.
For more information, please visit BugBot documentation.
Updated•2 days ago
|
Description
•