1 GOOGLE INVESTIGATING ISSUE WITH BLURRY FONTS ON NEW CHROME 69
4 Thursday September 06, 2018 @11:30PM (msmash)
5 from the blurry-texts dept.
7 o Reference: 0102638976
8 o News link: https://tech.slashdot.org/story/18/09/06/1839242/google-investigating-issue-with-blurry-fonts-on-new-chrome-69
9 o Source link: https://www.zdnet.com/article/google-investigating-issue-with-blurry-fonts-on-new-chrome-69/
12 Since the [1]release of Chrome 69 earlier this week ,
13 countless of users have gone on social media and Google
14 Product Forums to [2]complain about "blurry" or "fuzzy" text
15 inside Chrome . ZDNet:
17 > The blurred font issue isn't only limited to text rendered
18 inside a web page, users said, but also for the text
19 suggestions displayed inside the address bar search drop-down,
20 and Chrome's Developer Tools panel. [...] According to
21 reports, the issue only manifests for Chrome 69 users on
22 Windows. Those who rolled back to Chrome 68 stopped having
23 problems. Users said that changing Chrome, operating system,
24 or screen DPI settings didn't help. "Our team is investigating
25 reports of this behavior. You can find more information in
26 this public bug report," a Google spokesperson said last night
27 after first user complaints started surfacing online.
29 Some users have also expressed concerns over Chrome not
30 showing [3]"trivial subdomains" including www and secure lock
31 sign in the address bar.
35 [1] https://tech.slashdot.org/story/18/09/04/1711250/chrome-69-
36 arrives-with-revamped-design-more-powerful-omnibox-and-better-
39 [2] https://www.zdnet.com/article/google-investigating-issue-w-
40 ith-blurry-fonts-on-new-chrome-69/
42 [3] https://bugs.chromium.org/p/chromium/issues/detail?id=8814-
46 ** Whats the deal (Score:2)
47 (by 110010001000 ( 697113 ))
50 Whats the deal with the new interface. Looks like we are back to
51 rounded corners again.
56 (by 110010001000 ( 697113 ))
59 And what's the deal with decaf coffee? How do they get the
60 caffeine out of there, and then where does it go?
66 Why do they put caffeine in coffee and then take it
68 And why if Chrome rendering fonts in the first place?
69 That's a job for the operating system.
72 ** Re: Whats the deal (Score:2)
73 (by spongman ( 182339 ))
76 dichloromethe (or ethyl acetate) leeching.
81 (by DontBeAMoran ( 4843879 ))
84 Score: 5, That's gold Jerry, GOLD!
88 ** So Chrome 69 makes you blind? (Score:4, Funny)
89 (by the_skywise ( 189793 ))
92 The jokes write themselves...
94 ** Blurry Fonts... (Score:2)
95 (by Oswald McWeany ( 2428506 ))
98 Maybe they need to put on their Google Glass so they can read
102 (by Z00L00K ( 682162 ))
105 They just started to use Cleartype and the fuzzy fonts.
106 Both cleartype and fuzzy fonts gives me a headache so I have
107 to use uBlock to revert to the browser default when I run
111 ** I bet you (Score:5, Insightful)
112 (by The MAZZTer ( 911996 ))
115 If these are Windows users they screwed with the Compatibility
116 Mode options for DPI in order to make the window smaller or
117 bigger. It looked fine until Google did something differently
118 and now the Compatibility Mode options make it look blurry.
119 Turns out using options designed for use on legacy applications
120 only on modern applications introduces problems. Lots of Steam
121 users have similar problems.
124 (by omnichad ( 1198475 ))
127 Wrong. I use the standard DPI settings for the whole screen
128 (1.5x on my 27" 4K screen), which only works with programs
129 that are DPI-aware. It's true that I didn't notice the blurry
130 fonts until I saw the headline, but I really just thought I
131 was that tired (I've only had 69 for about a day). At least
132 for me, it's fairly mild.
137 (by omnichad ( 1198475 ))
140 If it looks significantly worse, it could also have
141 nothing at all to do with the bug - Chrome is DPI aware
142 and should never have that enabled. Especially since
143 the bug report doesn't have any mention of anything but
144 the system DPI setting.
151 (by omnichad ( 1198475 ))
154 So you like the way I word it (No Giggity).
160 (by Solandri ( 704621 ))
163 The problem is there are three ways to tweak the DPI.
164 Compatibility Mode, which can be set on a per-app basis.
165 Display scaling, which is set via the Windows desktop and
166 affects everything. And Advanced Scaling which Microsoft
167 introduced with the Spring Creators Update, which I haven't
168 figured out exactly how it's different from the regular
171 Under the hood, there's also ClearType which runs on top of
172 DPI scaling, and does [1]subpixel rendering [grc.com] (using
173 the individual red, green, and blue subp
178 [1] https://www.grc.com/ctwhat.htm
181 (by omnichad ( 1198475 ))
184 Looking at some zoomed in screenshots, I think they're
185 scaling the subpixel rendering itself (which should never
186 happen). There is no reason to have red or blue tint on
187 anything but the outermost pixel, but looking at my
188 screenshot close up I'm seeing two side-by-side bluish or
194 (by Scoth ( 879800 ))
197 Even on Chrome 69 on my multi-DPI work setup I have to turn
198 on the DPI scaling compatibility mode/override to not get
199 huge dialog boxes and widgets. It's a bit frustrating to me
200 that a currently supported, modern app would still have
205 (by Ingenium13 ( 162116 ))
208 Nope, I have a Windows VM that's essentially stock that I use
209 for a couple applications. I had Chrome open in it earlier
210 today, and noticed that the fonts were blurry and were giving
211 me a headache after a few minutes of use. I thought maybe it
212 was something with RDP messing it up, but after I read this,
213 I logged in again and verified that the fuzzy fonts are only
214 in Chrome. All other applications are fine.
218 (by greenwow ( 3635575 ))
221 And most Windows apps. For most of our users on Windows 10,
222 Windows apps have blurry text no matter what settings we try.
223 That really sucks for developers that need to read a lot of
229 ** Re: I bet you (Score:2)
230 (by spongman ( 182339 ))
238 (by Tailhook ( 98486 ))
241 Chrome has been having this problem for certain desktop users
242 for a while now. There are workaround flags and whatnot. Just
243 another chronic quality problem in Chrome that never gets
247 (by MidSpeck ( 1516577 ))
250 True. I had to disable "Accelerated 2D canvas" in order to
251 get the fuzziness to go away on mine on Chrome 68, which was
252 working just fine before that.
258 (by Z34107 ( 925136 ))
261 Text wrapping is a "solved" problem, too, but you're still
262 doing it by hand for some reason.
265 ** While they're at it (Score:2)
266 (by Pedestrianwolf ( 1591767 ))
269 ..maybe they could also roll back all rounded rectangles they
270 added in v69. Everything is so round it feels like I designed it
274 (by ArchieBunker ( 132337 ))
277 Chrome has a major UI re-design? Firefox is going to be
278 pulling some late nights to catch up!
281 ** It's also has performance regressions (Score:2)
282 (by Suren Enfiajyan ( 4600031 ))
285 On my Lenovo G570 the latest chrome also has very high CPU usage
286 on [1]slither.io game [slither.io] and the game turns into a
287 slideshow in places with many snakes. Firefox 61 doesn't suffer
288 from the this problem, despite the fact that its slower almost
289 in any regard. But not this time.
294 [1] http://slither.io/
297 (by jimbrooking ( 1909170 ))
300 After installing ALL pages I visit are pure black. No text or
304 (by jimbrooking ( 1909170 ))
307 Fix (Win 7 Home): Uninstall Chrome, delete all browsing date.
308 reinstall Chrome, be dazzled by the curviness.
311 ** Can someone summarize the linked article? (Score:4, Funny)
312 (by kaizendojo ( 956951 ))
315 I upgraded and I can't read it.
317 ** See Jeff Probst ... (Score:2)
318 (by CaptainDork ( 3678879 ))
322 I remember on Survivor®, back in the day, they had a "blurry
324 They fixed that by disallowing exposed tits.
325 Google should remove the tits from their fonts.
327 ** trivial subdomain hiding (Score:2)
328 (by Zaiff Urgulbunger ( 591514 ))
331 So this "trivial subdomain hiding" thing... it's a crap idea
334 ** Here's my take as a Mac user (Score:2)
335 (by DontBeAMoran ( 4843879 ))
338 First of all, I really hate these thin fonts. They may look neat
339 on hi-DPI displays but not everyone has one.
340 Secondly, the text on the left screen capture looks like it had
341 its pixels hammered to the nearest pixel, which is the typical
342 crappy-looking Microsoft anti-aliasing while the text on the
343 right looks like normal anti-aliased text to me.