Commit | Line | Data |
---|---|---|
299a08f3 NR |
1 | GOOGLE INVESTIGATING ISSUE WITH BLURRY FONTS ON NEW CHROME 69 \r |
2 | (ZDNET.COM) \r | |
3 | \r | |
4 | Thursday September 06, 2018 @11:30PM (msmash)\r | |
5 | from the blurry-texts dept.\r | |
6 | \r | |
7 | o News link: https://tech.slashdot.org/story/18/09/06/1839242/google-investigating-issue-with-blurry-fonts-on-new-chrome-69\r | |
8 | o Source link: https://www.zdnet.com/article/google-investigating-issue-with-blurry-fonts-on-new-chrome-69/\r | |
9 | \r | |
10 | \r | |
11 | Since the release of Chrome 69 earlier this week, countless of\r | |
12 | users have gone on social media and Google Product Forums to\r | |
13 | complain about "blurry" or "fuzzy" text inside Chrome. ZDNet:\r | |
14 | The blurred font issue isn't only limited to text rendered\r | |
15 | inside a web page, users said, but also for the text\r | |
16 | suggestions displayed inside the address bar search drop-down,\r | |
17 | and Chrome's Developer Tools panel. [...] According to\r | |
18 | reports, the issue only manifests for Chrome 69 users on\r | |
19 | Windows. Those who rolled back to Chrome 68 stopped having\r | |
20 | problems. Users said that changing Chrome, operating system,\r | |
21 | or screen DPI settings didn't help. "Our team is investigating\r | |
22 | reports of this behavior. You can find more information in\r | |
23 | this public bug report," a Google spokesperson said last night\r | |
24 | after first user complaints started surfacing online. Some\r | |
25 | users have also expressed concerns over Chrome not showing\r | |
26 | "trivial subdomains" including www and secure lock sign in the\r | |
27 | address bar.\r | |
28 | \r | |
29 | \r | |
30 | ** Whats the deal (Score:2)\r | |
31 | (by 110010001000 ( 697113 ))\r | |
32 | \r | |
33 | \r | |
34 | Whats the deal with the new interface. Looks like we are back to\r | |
35 | rounded corners again.\r | |
36 | \r | |
37 | ** \r | |
38 | \r | |
39 | ** Re: (Score:1)\r | |
40 | (by 110010001000 ( 697113 ))\r | |
41 | \r | |
42 | \r | |
43 | And what's the deal with decaf coffee? How do they get the\r | |
44 | caffeine out of there, and then where does it go?\r | |
45 | \r | |
46 | ** Re: (Score:1)\r | |
47 | (by Anonymous Coward)\r | |
48 | \r | |
49 | \r | |
50 | Why do they put caffeine in coffee and then take it\r | |
51 | back out?\r | |
52 | And why if Chrome rendering fonts in the first place?\r | |
53 | That's a job for the operating system.\r | |
54 | \r | |
55 | \r | |
56 | ** Re: Whats the deal (Score:2)\r | |
57 | (by spongman ( 182339 ))\r | |
58 | \r | |
59 | \r | |
60 | dichloromethe (or ethyl acetate) leeching.\r | |
61 | \r | |
62 | \r | |
63 | \r | |
64 | ** Re: (Score:2)\r | |
65 | (by DontBeAMoran ( 4843879 ))\r | |
66 | \r | |
67 | \r | |
68 | Score: 5, That's gold Jerry, GOLD!\r | |
69 | \r | |
70 | \r | |
71 | \r | |
72 | ** So Chrome 69 makes you blind? (Score:4, Funny)\r | |
73 | (by the_skywise ( 189793 ))\r | |
74 | \r | |
75 | \r | |
76 | The jokes write themselves...\r | |
77 | \r | |
78 | ** Blurry Fonts... (Score:2)\r | |
79 | (by Oswald McWeany ( 2428506 ))\r | |
80 | \r | |
81 | \r | |
82 | Maybe they need to put on their Google Glass so they can read\r | |
83 | the fonts clearer.\r | |
84 | \r | |
85 | ** Re: (Score:3)\r | |
86 | (by Z00L00K ( 682162 ))\r | |
87 | \r | |
88 | \r | |
89 | They just started to use Cleartype and the fuzzy fonts.\r | |
90 | Both cleartype and fuzzy fonts gives me a headache so I have\r | |
91 | to use uBlock to revert to the browser default when I run\r | |
92 | Firefox.\r | |
93 | \r | |
94 | \r | |
95 | ** I bet you (Score:5, Insightful)\r | |
96 | (by The MAZZTer ( 911996 ))\r | |
97 | \r | |
98 | \r | |
99 | If these are Windows users they screwed with the Compatibility\r | |
100 | Mode options for DPI in order to make the window smaller or\r | |
101 | bigger. It looked fine until Google did something differently\r | |
102 | and now the Compatibility Mode options make it look blurry.\r | |
103 | Turns out using options designed for use on legacy applications\r | |
104 | only on modern applications introduces problems. Lots of Steam\r | |
105 | users have similar problems.\r | |
106 | \r | |
107 | ** Re: (Score:2)\r | |
108 | (by omnichad ( 1198475 ))\r | |
109 | \r | |
110 | \r | |
111 | Wrong. I use the standard DPI settings for the whole screen\r | |
112 | (1.5x on my 27" 4K screen), which only works with programs\r | |
113 | that are DPI-aware. It's true that I didn't notice the blurry\r | |
114 | fonts until I saw the headline, but I really just thought I\r | |
115 | was that tired (I've only had 69 for about a day). At least\r | |
116 | for me, it's fairly mild.\r | |
117 | \r | |
118 | ** \r | |
119 | \r | |
120 | ** Re: (Score:2)\r | |
121 | (by omnichad ( 1198475 ))\r | |
122 | \r | |
123 | \r | |
124 | If it looks significantly worse, it could also have\r | |
125 | nothing at all to do with the bug - Chrome is DPI aware\r | |
126 | and should never have that enabled. Especially since\r | |
127 | the bug report doesn't have any mention of anything but\r | |
128 | the system DPI setting.\r | |
129 | \r | |
130 | \r | |
131 | \r | |
132 | ** \r | |
133 | \r | |
134 | ** Re: (Score:2)\r | |
135 | (by omnichad ( 1198475 ))\r | |
136 | \r | |
137 | \r | |
138 | So you like the way I word it (No Giggity).\r | |
139 | \r | |
140 | \r | |
141 | \r | |
142 | \r | |
143 | ** Re: (Score:3)\r | |
144 | (by Solandri ( 704621 ))\r | |
145 | \r | |
146 | \r | |
147 | The problem is there are three ways to tweak the DPI.\r | |
148 | Compatibility Mode, which can be set on a per-app basis.\r | |
149 | Display scaling, which is set via the Windows desktop and\r | |
150 | affects everything. And Advanced Scaling which Microsoft\r | |
151 | introduced with the Spring Creators Update, which I haven't\r | |
152 | figured out exactly how it's different from the regular\r | |
153 | Display Scaling.\r | |
154 | \r | |
155 | Under the hood, there's also ClearType which runs on top of\r | |
156 | DPI scaling, and does [1]subpixel rendering [grc.com] (using\r | |
157 | the individual red, green, and blue subp\r | |
158 | \r | |
159 | \r | |
160 | \r | |
161 | \r | |
162 | [1] https://www.grc.com/ctwhat.htm\r | |
163 | \r | |
164 | ** Re: (Score:2)\r | |
165 | (by omnichad ( 1198475 ))\r | |
166 | \r | |
167 | \r | |
168 | Looking at some zoomed in screenshots, I think they're\r | |
169 | scaling the subpixel rendering itself (which should never\r | |
170 | happen). There is no reason to have red or blue tint on\r | |
171 | anything but the outermost pixel, but looking at my\r | |
172 | screenshot close up I'm seeing two side-by-side bluish or\r | |
173 | reddish pixels.\r | |
174 | \r | |
175 | \r | |
176 | \r | |
177 | ** Re: (Score:2)\r | |
178 | (by Scoth ( 879800 ))\r | |
179 | \r | |
180 | \r | |
181 | Even on Chrome 69 on my multi-DPI work setup I have to turn\r | |
182 | on the DPI scaling compatibility mode/override to not get\r | |
183 | huge dialog boxes and widgets. It's a bit frustrating to me\r | |
184 | that a currently supported, modern app would still have\r | |
185 | problems with that.\r | |
186 | \r | |
187 | \r | |
188 | ** Re: (Score:2)\r | |
189 | (by Ingenium13 ( 162116 ))\r | |
190 | \r | |
191 | \r | |
192 | Nope, I have a Windows VM that's essentially stock that I use\r | |
193 | for a couple applications. I had Chrome open in it earlier\r | |
194 | today, and noticed that the fonts were blurry and were giving\r | |
195 | me a headache after a few minutes of use. I thought maybe it\r | |
196 | was something with RDP messing it up, but after I read this,\r | |
197 | I logged in again and verified that the fuzzy fonts are only\r | |
198 | in Chrome. All other applications are fine.\r | |
199 | \r | |
200 | \r | |
201 | ** Re: (Score:2)\r | |
202 | (by greenwow ( 3635575 ))\r | |
203 | \r | |
204 | \r | |
205 | And most Windows apps. For most of our users on Windows 10,\r | |
206 | Windows apps have blurry text no matter what settings we try.\r | |
207 | That really sucks for developers that need to read a lot of\r | |
208 | text.\r | |
209 | \r | |
210 | \r | |
211 | ** \r | |
212 | \r | |
213 | ** Re: I bet you (Score:2)\r | |
214 | (by spongman ( 182339 ))\r | |
215 | \r | |
216 | \r | |
217 | They don't?\r | |
218 | \r | |
219 | \r | |
220 | \r | |
221 | ** Not new (Score:2)\r | |
222 | (by Tailhook ( 98486 ))\r | |
223 | \r | |
224 | \r | |
225 | Chrome has been having this problem for certain desktop users\r | |
226 | for a while now. There are workaround flags and whatnot. Just\r | |
227 | another chronic quality problem in Chrome that never gets\r | |
228 | fixed....\r | |
229 | \r | |
230 | ** Re: (Score:1)\r | |
231 | (by MidSpeck ( 1516577 ))\r | |
232 | \r | |
233 | \r | |
234 | True. I had to disable "Accelerated 2D canvas" in order to\r | |
235 | get the fuzziness to go away on mine on Chrome 68, which was\r | |
236 | working just fine before that.\r | |
237 | \r | |
238 | \r | |
239 | ** \r | |
240 | \r | |
241 | ** Re: (Score:2)\r | |
242 | (by Z34107 ( 925136 ))\r | |
243 | \r | |
244 | \r | |
245 | Text wrapping is a "solved" problem, too, but you're still\r | |
246 | doing it by hand for some reason.\r | |
247 | \r | |
248 | \r | |
249 | ** While they're at it (Score:2)\r | |
250 | (by Pedestrianwolf ( 1591767 ))\r | |
251 | \r | |
252 | \r | |
253 | ..maybe they could also roll back all rounded rectangles they\r | |
254 | added in v69. Everything is so round it feels like I designed it\r | |
255 | in my basement.\r | |
256 | \r | |
257 | ** Re: (Score:3)\r | |
258 | (by ArchieBunker ( 132337 ))\r | |
259 | \r | |
260 | \r | |
261 | Chrome has a major UI re-design? Firefox is going to be\r | |
262 | pulling some late nights to catch up!\r | |
263 | \r | |
264 | \r | |
265 | ** It's also has performance regressions (Score:2)\r | |
266 | (by Suren Enfiajyan ( 4600031 ))\r | |
267 | \r | |
268 | \r | |
269 | On my Lenovo G570 the latest chrome also has very high CPU usage\r | |
270 | on [1]slither.io game [slither.io] and the game turns into a\r | |
271 | slideshow in places with many snakes. Firefox 61 doesn't suffer\r | |
272 | from the this problem, despite the fact that its slower almost\r | |
273 | in any regard. But not this time.\r | |
274 | \r | |
275 | \r | |
276 | \r | |
277 | \r | |
278 | [1] http://slither.io/\r | |
279 | \r | |
280 | ** BSOD (Score:2)\r | |
281 | (by jimbrooking ( 1909170 ))\r | |
282 | \r | |
283 | \r | |
284 | After installing ALL pages I visit are pure black. No text or\r | |
285 | graphics.\r | |
286 | \r | |
287 | ** Re: (Score:2)\r | |
288 | (by jimbrooking ( 1909170 ))\r | |
289 | \r | |
290 | \r | |
291 | Fix (Win 7 Home): Uninstall Chrome, delete all browsing date.\r | |
292 | reinstall Chrome, be dazzled by the curviness.\r | |
293 | \r | |
294 | \r | |
295 | ** Can someone summarize the linked article? (Score:4, Funny)\r | |
296 | (by kaizendojo ( 956951 ))\r | |
297 | \r | |
298 | \r | |
299 | I upgraded and I can't read it.\r | |
300 | \r | |
301 | ** See Jeff Probst ... (Score:2)\r | |
302 | (by CaptainDork ( 3678879 ))\r | |
303 | \r | |
304 | \r | |
305 | ... about this.\r | |
306 | I remember on Survivor®, back in the day, they had a "blurry\r | |
307 | tit," problem.\r | |
308 | They fixed that by disallowing exposed tits.\r | |
309 | Google should remove the tits from their fonts.\r | |
310 | \r | |
311 | ** trivial subdomain hiding (Score:2)\r | |
312 | (by Zaiff Urgulbunger ( 591514 ))\r | |
313 | \r | |
314 | \r | |
315 | So this "trivial subdomain hiding" thing... it's a crap idea\r | |
316 | right?\r | |
317 | \r | |
318 | ** Here's my take as a Mac user (Score:2)\r | |
319 | (by DontBeAMoran ( 4843879 ))\r | |
320 | \r | |
321 | \r | |
322 | First of all, I really hate these thin fonts. They may look neat\r | |
323 | on hi-DPI displays but not everyone has one.\r | |
324 | Secondly, the text on the left screen capture looks like it had\r | |
325 | its pixels hammered to the nearest pixel, which is the typical\r | |
326 | crappy-looking Microsoft anti-aliasing while the text on the\r | |
327 | right looks like normal anti-aliased text to me.\r | |
328 | \r | |
329 | \r |