New issue
Advanced search Search tips

Issue 610563 link

Starred by 3 users

Issue metadata

Status: Duplicate
Merged: issue 583273
Owner:
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Not always using subpixel rendering / LCD font smoothing on OS X

Reported by t...@close.io, May 10 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/601.5.17 (KHTML, like Gecko) Version/9.1 Safari/601.5.17

Steps to reproduce the problem:
1. Make sure "Use LCD font smoothing when available" is checked in System Preferences > General.
2. Open any website containing text on a OS X Retina screen. 
3. If you zoom in / take a screenshot, you'll notice that subpixel anti-aliasing is not applied, i.e. the font smoothing is greyscale.
4. Also, if you open a website on a non-Retina screen, font smoothing is fine until it is moved to a Retina screen, where it disappears. Moving that same window back to the non-Retina screen doesn't restore subpixel smoothing, and fonts appear blurry.

What is the expected behavior?
Subpixel font rendering / LCD font smoothing should always be used if the OS X system setting is checked, just like in Safari.

What went wrong?
Subpixel font smoothing is disabled on Retina screens (it shouldn't).

Did this work before? No 

Chrome version: 51.0.2704.36  Channel: n/a
OS Version: OS X 10.11.4
Flash Version:
 
Components: -UI UI>Browser
Labels: Needs-Feedback
I'm having trouble replicating this issue. Can you provide a screenshot/screencast?

Comment 2 by t...@close.io, May 13 2016

The first screenshot shows Google Chrome running on a Retina MacBook Pro with LCD font smoothing enabled.

The second screenshot shows the URL bar zoomed in (from the first screenshot), where subpixel font smoothing is working properly (you can see this by the colorful anti-aliasing).

The third screenshot shows content zoomed in (from the first screenshot), where subpixel font smoothing is not working (it's using greyscale anti-aliasing). This happens not just on the About page, but on all websites.

I can record a screencast later in case you can't reproduce 4), but the attached screenshots should already demonstrate that there is an issue.
Screen Shot 2016-05-13 at 16.47.55.png
167 KB View Download
Screen Shot 2016-05-13 at 16.48.35.png
32.4 KB View Download
Screen Shot 2016-05-13 at 16.49.00.png
40.9 KB View Download
Project Member

Comment 3 by sheriffbot@chromium.org, May 14 2016

Labels: -Needs-Feedback Needs-Review
Owner: spqc...@chromium.org
Thank you for providing more feedback. Adding requester "spqchan@chromium.org" for another review and adding "Needs-Review" label for tracking.

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

Comment 4 by kokok...@gmail.com, May 17 2016

I noticed this too, but on linux.
A test page is:
http://www.ilfattoquotidiano.it

Screenshot_20160517_163238.png
525 KB View Download
closeup.png
7.7 KB View Download
Labels: OS-Linux
Owner: ----

Comment 6 by tapted@chromium.org, Jun 15 2016

Components: Blink>Fonts
Owner: schenney@chromium.org
Status: Assigned (was: Unconfirmed)
[mac triage] chrome://help/ has layers (e.g., similar to chrome://settings/, scrolling causes the content to go underneath fixed-position stuff at the top of the page). I think we deliberately disable subpixel AA for some situations on retina devices only, since it gets computationally expensive to preserve it when layers get involved.

assigning to someone who may know more.

Possibly related to  Issue 381840 
Cc: schenney@chromium.org
Components: -UI>Browser -Blink>Fonts Blink>Compositing Blink>Scroll
Owner: flackr@chromium.org
On high-DPI screens, like retina, we deliberately disable sub-pixel font rendering in favor of improved scrolling performance. Specifically, the "--enable-prefer-compositing-to-lcd-text" flag is always true.

On linux there are probably cases where we disable lcd text but I am not expert on this. Assigning to someone who knows even more and is currently working on related issues.

There may be a bug here if we do not revert back to sub-pixel text when the monitor changes and we have information that would let us do so.

Comment 8 by flackr@chromium.org, Nov 22 2016

Mergedinto: 583273
Status: Duplicate (was: Assigned)
Yes, that is correct. This issue has been reported for linux previously as  issue 583273  and we have talked about what the threshold should be on  issue 242643 .

See https://cs.chromium.org/chromium/src/content/renderer/render_view_impl.cc?dr=CSs&q=DeviceScaleEnsuresTextQuality&sq=package:chromium&l=334 for whether we are willing to promote elements into composited layers even if they will lose LCD text and https://cs.chromium.org/chromium/src/content/renderer/render_view_impl.cc?dr=CSs&q=DeviceScaleEnsuresTextQuality&sq=package:chromium&l=334 for whether LCD text rendering is enabled. You might be able to enable LCD Text antialiasing in chrome://flags/#lcd-text-aa to force this to prefer anti-aliasing to compositing but keep in mind this will result in less responsive scrolling due to needing to repaint.

Sign in to add a comment