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