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 News link: https://tech.slashdot.org/story/18/09/06/1839242/google-investigating-issue-with-blurry-fonts-on-new-chrome-69
8 o Source link: https://www.zdnet.com/article/google-investigating-issue-with-blurry-fonts-on-new-chrome-69/
11 Since the release of Chrome 69 earlier this week, countless of
12 users have gone on social media and Google Product Forums to
13 complain about "blurry" or "fuzzy" text inside Chrome. ZDNet:
14 The blurred font issue isn't only limited to text rendered
15 inside a web page, users said, but also for the text
16 suggestions displayed inside the address bar search drop-down,
17 and Chrome's Developer Tools panel. [...] According to
18 reports, the issue only manifests for Chrome 69 users on
19 Windows. Those who rolled back to Chrome 68 stopped having
20 problems. Users said that changing Chrome, operating system,
21 or screen DPI settings didn't help. "Our team is investigating
22 reports of this behavior. You can find more information in
23 this public bug report," a Google spokesperson said last night
24 after first user complaints started surfacing online. Some
25 users have also expressed concerns over Chrome not showing
26 "trivial subdomains" including www and secure lock sign in the
30 ** Whats the deal (Score:2)
31 (by 110010001000 ( 697113 ))
34 Whats the deal with the new interface. Looks like we are back to
35 rounded corners again.
40 (by 110010001000 ( 697113 ))
43 And what's the deal with decaf coffee? How do they get the
44 caffeine out of there, and then where does it go?
50 Why do they put caffeine in coffee and then take it
52 And why if Chrome rendering fonts in the first place?
53 That's a job for the operating system.
56 ** Re: Whats the deal (Score:2)
57 (by spongman ( 182339 ))
60 dichloromethe (or ethyl acetate) leeching.
65 (by DontBeAMoran ( 4843879 ))
68 Score: 5, That's gold Jerry, GOLD!
72 ** So Chrome 69 makes you blind? (Score:4, Funny)
73 (by the_skywise ( 189793 ))
76 The jokes write themselves...
78 ** Blurry Fonts... (Score:2)
79 (by Oswald McWeany ( 2428506 ))
82 Maybe they need to put on their Google Glass so they can read
86 (by Z00L00K ( 682162 ))
89 They just started to use Cleartype and the fuzzy fonts.
90 Both cleartype and fuzzy fonts gives me a headache so I have
91 to use uBlock to revert to the browser default when I run
95 ** I bet you (Score:5, Insightful)
96 (by The MAZZTer ( 911996 ))
99 If these are Windows users they screwed with the Compatibility
100 Mode options for DPI in order to make the window smaller or
101 bigger. It looked fine until Google did something differently
102 and now the Compatibility Mode options make it look blurry.
103 Turns out using options designed for use on legacy applications
104 only on modern applications introduces problems. Lots of Steam
105 users have similar problems.
108 (by omnichad ( 1198475 ))
111 Wrong. I use the standard DPI settings for the whole screen
112 (1.5x on my 27" 4K screen), which only works with programs
113 that are DPI-aware. It's true that I didn't notice the blurry
114 fonts until I saw the headline, but I really just thought I
115 was that tired (I've only had 69 for about a day). At least
116 for me, it's fairly mild.
121 (by omnichad ( 1198475 ))
124 If it looks significantly worse, it could also have
125 nothing at all to do with the bug - Chrome is DPI aware
126 and should never have that enabled. Especially since
127 the bug report doesn't have any mention of anything but
128 the system DPI setting.
135 (by omnichad ( 1198475 ))
138 So you like the way I word it (No Giggity).
144 (by Solandri ( 704621 ))
147 The problem is there are three ways to tweak the DPI.
148 Compatibility Mode, which can be set on a per-app basis.
149 Display scaling, which is set via the Windows desktop and
150 affects everything. And Advanced Scaling which Microsoft
151 introduced with the Spring Creators Update, which I haven't
152 figured out exactly how it's different from the regular
155 Under the hood, there's also ClearType which runs on top of
156 DPI scaling, and does [1]subpixel rendering [grc.com] (using
157 the individual red, green, and blue subp
162 [1] https://www.grc.com/ctwhat.htm
165 (by omnichad ( 1198475 ))
168 Looking at some zoomed in screenshots, I think they're
169 scaling the subpixel rendering itself (which should never
170 happen). There is no reason to have red or blue tint on
171 anything but the outermost pixel, but looking at my
172 screenshot close up I'm seeing two side-by-side bluish or
178 (by Scoth ( 879800 ))
181 Even on Chrome 69 on my multi-DPI work setup I have to turn
182 on the DPI scaling compatibility mode/override to not get
183 huge dialog boxes and widgets. It's a bit frustrating to me
184 that a currently supported, modern app would still have
189 (by Ingenium13 ( 162116 ))
192 Nope, I have a Windows VM that's essentially stock that I use
193 for a couple applications. I had Chrome open in it earlier
194 today, and noticed that the fonts were blurry and were giving
195 me a headache after a few minutes of use. I thought maybe it
196 was something with RDP messing it up, but after I read this,
197 I logged in again and verified that the fuzzy fonts are only
198 in Chrome. All other applications are fine.
202 (by greenwow ( 3635575 ))
205 And most Windows apps. For most of our users on Windows 10,
206 Windows apps have blurry text no matter what settings we try.
207 That really sucks for developers that need to read a lot of
213 ** Re: I bet you (Score:2)
214 (by spongman ( 182339 ))
222 (by Tailhook ( 98486 ))
225 Chrome has been having this problem for certain desktop users
226 for a while now. There are workaround flags and whatnot. Just
227 another chronic quality problem in Chrome that never gets
231 (by MidSpeck ( 1516577 ))
234 True. I had to disable "Accelerated 2D canvas" in order to
235 get the fuzziness to go away on mine on Chrome 68, which was
236 working just fine before that.
242 (by Z34107 ( 925136 ))
245 Text wrapping is a "solved" problem, too, but you're still
246 doing it by hand for some reason.
249 ** While they're at it (Score:2)
250 (by Pedestrianwolf ( 1591767 ))
253 ..maybe they could also roll back all rounded rectangles they
254 added in v69. Everything is so round it feels like I designed it
258 (by ArchieBunker ( 132337 ))
261 Chrome has a major UI re-design? Firefox is going to be
262 pulling some late nights to catch up!
265 ** It's also has performance regressions (Score:2)
266 (by Suren Enfiajyan ( 4600031 ))
269 On my Lenovo G570 the latest chrome also has very high CPU usage
270 on [1]slither.io game [slither.io] and the game turns into a
271 slideshow in places with many snakes. Firefox 61 doesn't suffer
272 from the this problem, despite the fact that its slower almost
273 in any regard. But not this time.
278 [1] http://slither.io/
281 (by jimbrooking ( 1909170 ))
284 After installing ALL pages I visit are pure black. No text or
288 (by jimbrooking ( 1909170 ))
291 Fix (Win 7 Home): Uninstall Chrome, delete all browsing date.
292 reinstall Chrome, be dazzled by the curviness.
295 ** Can someone summarize the linked article? (Score:4, Funny)
296 (by kaizendojo ( 956951 ))
299 I upgraded and I can't read it.
301 ** See Jeff Probst ... (Score:2)
302 (by CaptainDork ( 3678879 ))
306 I remember on Survivor®, back in the day, they had a "blurry
308 They fixed that by disallowing exposed tits.
309 Google should remove the tits from their fonts.
311 ** trivial subdomain hiding (Score:2)
312 (by Zaiff Urgulbunger ( 591514 ))
315 So this "trivial subdomain hiding" thing... it's a crap idea
318 ** Here's my take as a Mac user (Score:2)
319 (by DontBeAMoran ( 4843879 ))
322 First of all, I really hate these thin fonts. They may look neat
323 on hi-DPI displays but not everyone has one.
324 Secondly, the text on the left screen capture looks like it had
325 its pixels hammered to the nearest pixel, which is the typical
326 crappy-looking Microsoft anti-aliasing while the text on the
327 right looks like normal anti-aliased text to me.