Google Investigating Issue With Blurry Fonts on new Chrome 69 (zdnet.com) 71
Since the release of Chrome 69 earlier this week, countless of users have gone on social media and Google Product Forums to complain about "blurry" or "fuzzy" text inside Chrome. ZDNet: The blurred font issue isn't only limited to text rendered inside a web page, users said, but also for the text suggestions displayed inside the address bar search drop-down, and Chrome's Developer Tools panel. [...] According to reports, the issue only manifests for Chrome 69 users on Windows. Those who rolled back to Chrome 68 stopped having problems. Users said that changing Chrome, operating system, or screen DPI settings didn't help. "Our team is investigating reports of this behavior. You can find more information in this public bug report," a Google spokesperson said last night after first user complaints started surfacing online. Some users have also expressed concerns over Chrome not showing "trivial subdomains" including www and secure lock sign in the address bar.
Whats the deal (Score:2)
Re: (Score:1)
Re: (Score:1)
Why do they put caffeine in coffee and then take it back out?
And why if Chrome rendering fonts in the first place? That's a job for the operating system.
Re: Whats the deal (Score:2)
dichloromethe (or ethyl acetate) leeching.
Re: (Score:2)
Score: 5, That's gold Jerry, GOLD!
So Chrome 69 makes you blind? (Score:5, Funny)
Blurry Fonts... (Score:2)
Maybe they need to put on their Google Glass so they can read the fonts clearer.
Re: (Score:3)
They just started to use Cleartype and the fuzzy fonts.
Both cleartype and fuzzy fonts gives me a headache so I have to use uBlock to revert to the browser default when I run Firefox.
I bet you (Score:5, Insightful)
Re: (Score:2)
Wrong. I use the standard DPI settings for the whole screen (1.5x on my 27" 4K screen), which only works with programs that are DPI-aware. It's true that I didn't notice the blurry fonts until I saw the headline, but I really just thought I was that tired (I've only had 69 for about a day). At least for me, it's fairly mild.
Re: (Score:2)
If it looks significantly worse, it could also have nothing at all to do with the bug - Chrome is DPI aware and should never have that enabled. Especially since the bug report doesn't have any mention of anything but the system DPI setting.
Re: (Score:2)
So you like the way I word it (No Giggity).
Re:I bet you (Score:4, Informative)
Under the hood, there's also ClearType which runs on top of DPI scaling, and does subpixel rendering [grc.com] (using the individual red, green, and blue subpixels to sharpen fonts). So there's a lot of places other than Compatibility Mode where something could go wrong to cause blurry fonts. My bet would actually be on the new Advanced Scaling options which were added - they're probably doing something which couldn't happen before with Display Scaling was your only option, and which only crops up if you have those two tweaked a certain way.
Re: (Score:2)
Looking at some zoomed in screenshots, I think they're scaling the subpixel rendering itself (which should never happen). There is no reason to have red or blue tint on anything but the outermost pixel, but looking at my screenshot close up I'm seeing two side-by-side bluish or reddish pixels.
Re: (Score:2)
Even on Chrome 69 on my multi-DPI work setup I have to turn on the DPI scaling compatibility mode/override to not get huge dialog boxes and widgets. It's a bit frustrating to me that a currently supported, modern app would still have problems with that.
Re: (Score:2)
Nope, I have a Windows VM that's essentially stock that I use for a couple applications. I had Chrome open in it earlier today, and noticed that the fonts were blurry and were giving me a headache after a few minutes of use. I thought maybe it was something with RDP messing it up, but after I read this, I logged in again and verified that the fuzzy fonts are only in Chrome. All other applications are fine.
Re: (Score:2)
And most Windows apps. For most of our users on Windows 10, Windows apps have blurry text no matter what settings we try. That really sucks for developers that need to read a lot of text.
Re: (Score:2)
At some point you just need to get your developers glasses or fire your IT team.
Re: I bet you (Score:2)
They don't?
Not new (Score:2)
Chrome has been having this problem for certain desktop users for a while now. There are workaround flags and whatnot. Just another chronic quality problem in Chrome that never gets fixed....
Re: (Score:1)
True. I had to disable "Accelerated 2D canvas" in order to get the fuzziness to go away on mine on Chrome 68, which was working just fine before that.
Re: (Score:2)
Text wrapping is a "solved" problem, too, but you're still doing it by hand for some reason.
While they're at it (Score:2)
Re:While they're at it (Score:4, Funny)
Chrome has a major UI re-design? Firefox is going to be pulling some late nights to catch up!
Re: (Score:2)
..maybe they could also roll back all rounded rectangles they added in v69. Everything is so round it feels like I designed it in my basement.
Yeah, it's starting to look like Slashdot.
It's also has performance regressions (Score:2)
BSOD (Score:2)
Re: (Score:2)
Can someone summarize the linked article? (Score:5, Funny)
See Jeff Probst ... (Score:2)
... about this.
I remember on Survivor®, back in the day, they had a "blurry tit," problem.
They fixed that by disallowing exposed tits.
Google should remove the tits from their fonts.
trivial subdomain hiding (Score:2)
Here's my take as a Mac user (Score:2)
First of all, I really hate these thin fonts. They may look neat on hi-DPI displays but not everyone has one.
Secondly, the text on the left screen capture looks like it had its pixels hammered to the nearest pixel, which is the typical crappy-looking Microsoft anti-aliasing while the text on the right looks like normal anti-aliased text to me.