I second this. It has to do with Directwrite, the ability to disable it was removed in recent Chrome versions. Just add it back and the problem disappears.

This is indeed due to the --disable-direct-write flag no longer being available. You may tweak the rendeirng of direct write text using the windows font settings to suite your needs. 

I am facing the same issue. It also affects Urdu language font and outputs are really horrible.

WontFix? Just goes to show how idiotic Chromium developers are.

Windows font settings do nothing to fix this issue. The issue is only in Blink, Firefox displays fonts just fine and apparently you want everyone to use Firefox instead of Blink.

Agreed. With the latest Chrome update (I'm running Windows 10) now my inbox is bolded and certain web pages have small font. This has been an issue in Chrome for years. I had DirectWrite disabled and that was the solution but now it's gone in the flag settings?? Why?? Bring it back and problem solved. 

Deleted: inbox.png 49.3 KB

	inbox.png 49.3 KB View Download

Deleted: Chrome Browser.png 177 KB

	Chrome Browser.png 177 KB View Download

Same issue here and following the advice of a person on the Chrome forum I went to to chrome://flags/ and disabled DirectWrite font rendering system (switched #disable-direct-write on).

Big improvement even if there are still some font rendering issues. But I can use Slack again and read my mail!

Thanks for the reply, but your solution is why I wrote. It was my solution. In my "Chrome flags" they no longer have direct-write. It's gone. In a Google search, I'm finding others who are saying it's gone as well. I did upgrade to Windows 10 and that's when the problem started but not sure why. I'm not sure why they did away with direct-write but it's not a choice anymore. Does anyone have any other ideas?

Your only option is switching to Firefox. They are not fixing the bug.

Mmmm...I'm wondering how it's not affecting more of the millions of users? Is it a bug on their end or is there some setting in my Windows 10 O.S. that Chrome doesn't like?

It's affecting every single computer I manage in my job (~250). I guess people don't realize it / don't care / don't want to report the bug?

good to know. i'm glad it's not just me. where are cried from the over-50 crowd that can't read the tiny thin font on half the pages?! 

i almost long for the days of user-controlled, maybe-once-per-year software updates! All of this daily/weekly forced app updating on my phone, ipad, computers - impossible to keep up. They used to call these updates - betas! But now betas are pushed out as "updates." I wish they could at least have easy access to downgrades and we could CHOOSE to update when WE wanted a new feature. Yeah, I know, security holes are the main reason for constant updating. Blah blah blah

Same problem here, Even after i resetted laptop

Same problem here. Please add back GDI font rendering. You are affecting millions by removing it. Looks like Firefox will be popular again.

I don't think this is related to removing GDI (and the --disable-direct-write flag), since that change did not land until M52, and this problem is being reported in M51.

Some users report that running the ClearType tuner fixes their problem, so this may be caused by something external to Chrome. I'm also looking into what might have caused antialiasing/subpixel problems in this timeframe.

+eae@ - can you think of anything that happened in M51 that might've caused AA to get turned off for some people?

+drott@, eae@ - can either of you think of anything that might have happened around early June or M51 that might have caused us to stop anti-aliasing text?

We changed the way we passed the windows system settings to the renderer in 51 so if the users have disabled AA in windows we'll now respect that.

Thanks for the update. Sounds like this is intended behavior as a consequence of  issue 419003 .

Users who are experiencing this problem should adjust their OS font settings if they want AA enabled.

 Issue 624899  has been merged into this issue.

 Issue 624353  has been merged into this issue.