Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Chrome Google Bug The Internet

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.
This discussion has been archived. No new comments can be posted.

Google Investigating Issue With Blurry Fonts on new Chrome 69

Comments Filter:
  • Whats the deal with the new interface. Looks like we are back to rounded corners again.
  • by the_skywise ( 189793 ) on Thursday September 06, 2018 @01:46PM (#57265240)
    The jokes write themselves...
  • Maybe they need to put on their Google Glass so they can read the fonts clearer.

    • by Z00L00K ( 682162 )

      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)

    by The MAZZTer ( 911996 ) <megazzt.gmail@com> on Thursday September 06, 2018 @01:58PM (#57265334) Homepage
    If these are Windows users they screwed with the Compatibility Mode options for DPI in order to make the window smaller or bigger. It looked fine until Google did something differently and now the Compatibility Mode options make it look blurry. Turns out using options designed for use on legacy applications only on modern applications introduces problems. Lots of Steam users have similar problems.
    • 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:I bet you (Score:4, Informative)

      by Solandri ( 704621 ) on Thursday September 06, 2018 @02:15PM (#57265438)
      The problem is there are three ways to tweak the DPI. Compatibility Mode, which can be set on a per-app basis. Display scaling, which is set via the Windows desktop and affects everything. And Advanced Scaling which Microsoft introduced with the Spring Creators Update, which I haven't figured out exactly how it's different from the regular Display Scaling.

      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.
      • 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.

    • by Scoth ( 879800 )

      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.

    • 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.

    • 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.

  • 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....

    • 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.

  • ..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.
  • On my Lenovo G570 the latest chrome also has very high CPU usage on slither.io game [slither.io] and the game turns into a slideshow in places with many snakes. Firefox 61 doesn't suffer from the this problem, despite the fact that its slower almost in any regard. But not this time.
  • After installing ALL pages I visit are pure black. No text or graphics.
    • Fix (Win 7 Home): Uninstall Chrome, delete all browsing date. reinstall Chrome, be dazzled by the curviness.
  • by kaizendojo ( 956951 ) on Thursday September 06, 2018 @04:07PM (#57265998)
    I upgraded and I can't read it.
  • ... 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.

  • So this "trivial subdomain hiding" thing... it's a crap idea right?
  • 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.

Ocean: A body of water occupying about two-thirds of a world made for man -- who has no gills. -- Ambrose Bierce

Working...