New issue
Advanced search Search tips

Issue 711317 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
danakj@chromium.org
flackr@chromium.org
xidac...@chromium.org
yigu@chromium.org
enne@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task



Sign in to add a comment

Add metric for how often we keep / lose LCD text on low DPI

Project Member Reported by flackr@chromium.org, Apr 13 2017 
On low DPI, we try to preserve subpixel anti-aliasing as it is a significant improvement in text rendering quality (issue 711312, issue 626200,  issue 381840 , etc), but we don't seem to currently track how successful we are.

We should add a metric that tracks how often or what proportion of web content is rendered with subpixel text antialiasing so that when making changes to compositing code we can track how this has changed over time.

This could be tracked for example, as a percentage of total layer area, to reflect that larger regions are more important than smaller ones.

Comment 1 by schenney@chromium.org, Apr 13 2017

Cc: flackr@chromium.org
Components: -Blink>Paint Blink>Compositing
Labels: BugSource-Team PaintTeamTriaged-20170413
Owner: ----
Wouldn't this work be done in the compositor, where subpixel text rendering usage is finally determined? Is that in the compositor thread?

"Available" with "Owner" is now discouraged. Moved flackr@ to CC.

Comment 2 by flackr@chromium.org, Apr 13 2017

Components: -Blink>Compositing Internals>Compositing
Yes, the final determination happens on the compositor so it would make sense to track there, which I think means Internals>Compositing?

Comment 3 by xidac...@chromium.org, Apr 26 2017

Owner: xidac...@chromium.org
Will investigate.
Project Member

Comment 4 by sheriffbot@chromium.org, Apr 27 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by sunn...@chromium.org, Apr 27 2018

Cc: danakj@chromium.org enne@chromium.org
Status: Available (was: Untriaged)
Seems useful to have this.

Comment 6 by xidac...@chromium.org, May 1 2018

Cc: xidac...@chromium.org
Owner: ----
►

Sign in to add a comment