OK, comments to the rescue:
1. Open a new tab and type in "chrome:flags" (without quotes) in the search bar
2. Do a Find (CTRL+F) for "DirectWrite" (Disable DirectWrite Windows) & Enable it
3. Close all of your Chrome browser (restart Chrome)
My forum fonts are back to normal now :thumbsup:
OK, comments to the rescue:
1. Open a new tab and type in "chrome:flags" (without quotes) in the search bar
2. Do a Find (CTRL+F) for "DirectWrite" (Disable DirectWrite Windows) & Enable it
3. Close all of your Chrome browser (restart Chrome)
My forum fonts are back to normal now :thumbsup:
No it doesn't. Firefox uses directwrite and looks fine.
THANK you. I had to do this because work forced the update on chrome. As someone else said, the Links bolded and sitting ON the link underline made it horrible to read.
OK, comments to the rescue:
1. Open a new tab and type in "chrome:flags" (without quotes) in the search bar
2. Do a Find (CTRL+F) for "DirectWrite" (Disable DirectWrite Windows) & Enable it
3. Close all of your Chrome browser (restart Chrome)
My forum fonts are back to normal now :thumbsup:
It's not hardware acceleration, it's hinting. (That link is very much worth a read, and the rest of this post assumes that you've read it or that you already understand what hinting is.)
Windows GDI font rendering is heavily hinted (it's why text on Windows looks so beautiful on low-DPI screens). However, the new hardware-accelerated APIs in Windows are, by default, unhinted (or very lightly hinted--I can't remember). This produces a more "faithful" text and text that scales more smoothly (e.g., if you have a text animation that grows the text from 10pt to 100pt, that animation will be smooth with unhinted rendering and will be jerky with hinted rendering).
When IE switched to hardware-accelerated text rendering, it got unhinted text. That's why some text looks a bit smaller than before, and why text don't look quite as sharp and clear as before.
When Firefox switched to hardware-accelerated text rendering, there was quite a bit of controversy, and a lot of people (including myself) argued that the benefits of hinting outweighed the downsides (most of the text that we see is static text for reading--we should thus optimize for on-screen readability, not for print fidelity or for text animations because, well, we know how people just loved the blink tag, right?). The compromise that was reached was that there was a list of fonts that would get the classic GDI-style full-on hinting treatment. This included the UI fonts like Segoe UI and all the common core web fonts like Arial and Verdana. This list of exemptions is configurable and can be found in about:config under "gfx.font_rendering.cleartype_params.force_gdi_classic_for_families". However, these exempted fonts still use hardware-accelerated rendering. It's just that Firefox is passing a parameter that says that it wants classic GDI-style hinting.
No amount of ClearType tuning would help when the problem is that text is being rendered with typeface fidelity given priority over on-screen legibility--this is not something that can be solved by tuning. And, yes, high-DPI will help since the effect of hinting diminishes as the the typeface occupies more pixels, but that's not really a solution, either.
No, the solution is to complain to Google and tell them that on-screen legibility is more important than print/typeface fidelity (seriously, how many people give a flying frack if a typeface doesn't look exactly what its designers intended, as long as it's crisp and legible?) and that you demand that they implement a Firefox-style solution where they use GPU-accelerated DirectWrite, but with nice pixel-friendly GDI-style hinting. That's the only solution that lets you use hardware acceleration while retaining good on-screen text (either that, or make that change yourself to the Chromium source code and compile your own version ).
Or... you could use the browser that gives users a choice in the matter: Firefox.
OK, comments to the rescue:
1. Open a new tab and type in "chrome:flags" (without quotes) in the search bar
2. Do a Find (CTRL+F) for "DirectWrite" (Disable DirectWrite Windows) & Enable it
3. Close all of your Chrome browser (restart Chrome)
My forum fonts are back to normal now :thumbsup:
Mine is already enabled when I checked but am having the problem. so now what?
Edit: You must have meant disable it. Don't know why you said enable it at the end, it's just confusing. I disabled it and it worked.
OK, comments to the rescue:
1. Open a new tab and type in "chrome:flags" (without quotes) in the search bar
2. Do a Find (CTRL+F) for "DirectWrite" (Disable DirectWrite Windows) & Enable it
3. Close all of your Chrome browser (restart Chrome)
My forum fonts are back to normal now :thumbsup:
So the font change finally impacted me, but the fix above worked to get it back to normal; thanks for that.
I have a different issue though, none of the dropdown menus work here now. For example if I click on "Your Notifications" and then click on "Unread Private Messages" nothing happens. If I try to right-click on it and "Open in new tab" all it does is re-open whatever thread I am currently in, in that new tab. Very obnoxious!
KT