New issue
Advanced search Search tips

Issue 891023 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Small text is kerned poorly on high-DPI display

Project Member Reported by derat@chromium.org, Oct 1

Issue description

Google Chrome	69.0.3497.95 (Official Build) (64-bit)
Revision	e3a5f87b64d44c4b311d2458f16b9f469e2597fb-refs/branch-heads/3497@{#931}
Platform	10895.56.0 (Official Build) stable-channel eve

When I convert this eve device to tablet mode and rotate it to a portrait orientation, small text like what I see on crbug.com has broken kerning -- some letters are squished up next to each other, while others have big gaps between them. I filed http://listnr/product/208/report/85695157742 after seeing this.

For example, in the tenth bug from the top in the listing, you can see that the 'u' and 'l' in "should" are touching, but there's a bunch of space between the 'l' and the 'd'.

There are a bunch of other examples near the bottom of the screenshot: "on", "supply", etc.

If I had to guess, maybe we're computing glyph positions as integer values at a lower DPI and then scaling them up.
 
Cc: afakhry@chromium.org
This could be due to interaction between auto-zoom in tablet mode and blink zoom.
Cc: bokan@chromium.org
CC bokan@
Cc: malaykeshav@chromium.org
Owner: ----
Clearing owner to make sure someone in fonts can triage.
Components: -UI>HighDPI -Blink>Fonts OS
Looks like the glyphs are positioned for a different geometry and then scaled. 
This appears to be ChromeOS specific (likely something not being configured properly in tablet mode or subpixel position being explicitly disabled).

Over to ChromeOS team for further triage.
Owner: afakhry@chromium.org
Oshima and Ahmed, are either of you the right person to look at this if it's an issue with how Chrome is configuring Blink?
Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Sign in to add a comment