Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
oops, sorry ignore this text below that's at the end of the repro steps-- forgot to delete draft text when submitting bug:
2. Open chrome to any web page using local (non-web) fonts.
3. If fonts are aliased
It should work fine.
Open any webpage that uses local fonts (not web fonts). The Google home page is one example.
2. Open chrome to any web page using local (non-web) fonts.
3. If fonts are aliased
It should work fine.
Open any webpage that uses local fonts (not web fonts). The Google home page is one example.
pb...@chromium.org
[Empty comment from Monorail migration]
[Deleted User] <[Deleted User]>
justin.grant@, thanks for the issue.
Could you please confirm if this is related tohttps://crbug.com/chromium/394692 .
Could you please confirm if this is related to
sc...@chromium.org
Not related to 394692.
sc...@chromium.org
We fiddled with disabling AA a while back https://codereview.chromium.org/342353003/
In the end Emil fixed it Blink-side I think. I'm not sure why there'd be a timing issue though.
+sky because he's the only person who disables it that I know of, and maybe has some complaints or seen this problem.
In the end Emil fixed it Blink-side I think. I'm not sure why there'd be a timing issue though.
+sky because he's the only person who disables it that I know of, and maybe has some complaints or seen this problem.
sk...@chromium.org
Some fonts still look WRONG. For example, 'M's on this site look like they were hit over the head with an ugly stick (see screenshot). But I would say that in general fonts are way better than when I had submitted that other bug. I no longer want to poke my eyes out.
[Deleted User] <[Deleted User]>
I installed latest canary (38.0.2123.0) and the problem now reproes 100% of the time. Fonts are always anti-aliased when I start Chrome, even though my OS settings disable font smoothing. Let me know how I can help you repro this problem. It makes Chrome unusable for me.
BTW, this is a different problem from what sky@ is reporting above. Sky@ is seeing aliased fonts, but they're poorly rendered. I'm seeing anti-aliased fonts even though my OS settings should prevent this.
FWIW, I believe that Firefox uses DirectWrite but seems to do a great job showing unsmoothed text. The attached image shows Chrome on top, Firefox 31 on bottom. FF's fonts are crisp and unsmoothed, while Chrome's are anti-aliased and (to my eyes) blurry and difficult to read.
Here's a blog post describing FF's support of DirectWrite in case it's useful.http://blog.mozilla.org/nattokirai/2011/08/11/directwrite-text-rendering-in-firefox-6/
BTW, this is a different problem from what sky@ is reporting above. Sky@ is seeing aliased fonts, but they're poorly rendered. I'm seeing anti-aliased fonts even though my OS settings should prevent this.
FWIW, I believe that Firefox uses DirectWrite but seems to do a great job showing unsmoothed text. The attached image shows Chrome on top, Firefox 31 on bottom. FF's fonts are crisp and unsmoothed, while Chrome's are anti-aliased and (to my eyes) blurry and difficult to read.
Here's a blog post describing FF's support of DirectWrite in case it's useful.
ea...@chromium.org
justin.grant: Disabling ClearType does not disable font smoothing, it just changes the type of font smoothing used. To completely disable font smoothing go to
Control Panel > System > Advanced System Settings > Performance > Settings
and uncheck the "Smooth edges of screen fonts" checkbox.
Control Panel > System > Advanced System Settings > Performance > Settings
and uncheck the "Smooth edges of screen fonts" checkbox.
as...@chromium.org
@justin.grant: Would you mind trying the above with the steps given in https://crbug.com/chromium/399504#c8 ? Let us know, if it works for you.
Thank you!
Thank you!
ph...@gmail.com
Right, I want to disable ClearType. The standard font smoothing is not blurry, it looks better than not smoothed at all. ClearType is blurry and should be turned off when the operating system setting for it is turned off.
[Deleted User] <[Deleted User]>
eae@ - you're correct. When I perform that extra step of unchecking "smooth edges of screen fonts", then smoothing turns off in Chrome-- and in Windows Explorer too which is nice to know.
That said, Firefox turns off smoothing when you uncheck "Turn on ClearType" checkbox which seems much more user-friendly. That second setting is much, much less well-known. Yes, it's Microsoft's fault for having two separate settings in totally different places to control smoothing (arrrgh!), but Firefox's solution to this sad state of affairs seems more reasonable than Chrome's.
I'd suggest that Chrome adopt the Firefox behavior: disable smoothing when the user disables either ClearType or the other "screen fonts" setting. IMHO this is better than requiring users to learn about both settings and also better than my reaction which was to think that Chrome was simply broken.
That said, Firefox turns off smoothing when you uncheck "Turn on ClearType" checkbox which seems much more user-friendly. That second setting is much, much less well-known. Yes, it's Microsoft's fault for having two separate settings in totally different places to control smoothing (arrrgh!), but Firefox's solution to this sad state of affairs seems more reasonable than Chrome's.
I'd suggest that Chrome adopt the Firefox behavior: disable smoothing when the user disables either ClearType or the other "screen fonts" setting. IMHO this is better than requiring users to learn about both settings and also better than my reaction which was to think that Chrome was simply broken.
ea...@chromium.org
Re #11:
Thanks for confirimg justin.grant. The cleartype checkbox is supposed to change the font smoothing settings not turn it off completely. We might have to change how we interpret that value going forward to match the behavior of IE and Firefox.
Thanks for confirimg justin.grant. The cleartype checkbox is supposed to change the font smoothing settings not turn it off completely. We might have to change how we interpret that value going forward to match the behavior of IE and Firefox.
[Deleted User] <[Deleted User]>
IE9+ completely ignores both settings and will never disable smoothing.
Firefox disables smoothing based on the cleartype checkbox. (perhaps the other smoothing checkbox will disable it too on FF-- I didn't check).
Chrome in previous (VDI) releases matched the Firefox behavior-- smoothing was disabled based on the cleartype checkbox.
Given that users who have trouble with smoothing have probably switched from IE long ago, it seems like a no-brainer to match FF and previous chrome behavior.
Firefox disables smoothing based on the cleartype checkbox. (perhaps the other smoothing checkbox will disable it too on FF-- I didn't check).
Chrome in previous (VDI) releases matched the Firefox behavior-- smoothing was disabled based on the cleartype checkbox.
Given that users who have trouble with smoothing have probably switched from IE long ago, it seems like a no-brainer to match FF and previous chrome behavior.
[Deleted User] <[Deleted User]>
BTW, do you want to remove the Needs-Feedback label on this issue?
am...@google.com
Moving all non essential bugs to the next Milestone.
[Deleted User] <[Deleted User]>
This issue has already been moved once and is lower than Priority 1,therefore removing mstone.
st...@gmail.com
Disabling the checkbox "Smooth edges of screen fonts" on Windows makes web fonts (which are usually not hinted as perfectly as system fonts like Arial and Verdana) nearly unreadable in Firefox (which is the only browser that obeys this Windows setting). Combined with the fact that a website cannot detect this situation (and fallback to a system font) this is a real problem for all websites using web fonts. Therefore I would not change the current Chrome behaviour.
Just my two cents a web developer.
Just my two cents a web developer.
cp...@chromium.org
[Empty comment from Monorail migration]
tk...@chromium.org
[Empty comment from Monorail migration]
[Deleted User] <[Deleted User]>
dt...@chromium.org
Removing Cr-Blink from issues that already have Cr-Blink sub-label set.
is...@google.com
This issue was migrated from crbug.com/chromium/399504?no_tracker_redirect=1
[Monorail mergedinto:crbug.com/chromium/419003 ]
[Monorail components added to Component Tags custom field.]
[Monorail mergedinto:
[Monorail components added to Component Tags custom field.]
Description
Example URL:
Steps to reproduce the problem:
1. Disable ClearType across the OS. To do this:
a. Control Panel\Appearance and Personalization\Display
b. Click "Adjust ClearType text" link on the left
c. Uncheck "Turn on ClearType"
d. Reboot
2. Open Firefox to Google home page. Fonts in HTML should be aliased (non-smoothed).
3. Open Chrome to Google home page.
4. If fonts are not smoothed, close Chrome, wait a few seconds and goto step 3. Sometimes it takes a few tries to repro.
Once the repro happens, all newly-opened chrome tabs will have the problem.
If you disable DirectWrite support in chrome://flags, then the problem goes away.
2. Open chrome to any web page using local (non-web) fonts.
3. If fonts are aliased
It should work fine.
Open any webpage that uses local fonts (not web fonts). The Google home page is one example.
What is the expected behavior?
Only web fonts are anti-aliased. All other fonts respect the OS's default font-smoothing setting.
What went wrong?
All fonts are anti-aliased, even non-web fonts.
Does it occur on multiple sites: Yes
Is it a problem with a plugin? No
Did this work before? Yes Not sure. FWIW, it seems to happen much less often with 37.0.2062.44 than 37.0.2062.58-- the older version almost never shows the problem, while the newer version seems to trigger it almost every time.
Does this work in other browsers? Yes
Chrome version: 37.0.2062.58 Channel: beta
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
Being able to turn off anti-aliasing is an important accessibility issue, because there's a small percentage of users for whom font smoothing on low-PPI monitors (almost all desktop monitors in use today) generates severe eyestrain.
This issue is separate from
FWIW, Firefox doesn't have this problem.
IE *does* have this problem, but that's because IE decided to always apply font smoothing and to ignore the OS's setting. I know the guys at Microsoft responsible for font rendering, and I've been hassling them to fix that bug for the last 8 years. Let's hope Chrome will be faster to fix it. ;-)