git://git.nikiroo.be / gofetch.git / blame
| Commit | Line | Data |
|---|---|---|
| 299a08f3 NR |
1 | <!DOCTYPE html> |
| 2 | <html> | |
| 3 | <head> | |
| 4 | <meta http-equiv='content-type' content='text/html; charset=utf-8'> | |
| 5 | <meta name='viewport' content='width=device-width, initial-scale=1.0'> | |
| 6 | <style type='text/css'> | |
| 7 | body { margin: 1em 15%; } | |
| 8 | </style> | |
| 9 | </head> | |
| 10 | <body> | |
| 11 | <div class='story'> | |
| c715ea02 | 12 | <h2>Google Investigating Issue With Blurry Fonts on new Chrome 69 (zdnet.com)</h2> |
| 299a08f3 NR |
13 | <div class='details'>(Thursday September 06, 2018 @11:30PM (msmash) |
| 14 | from the blurry-texts dept.)</div> | |
| 15 | <br/> | |
| 16 | <ul> | |
| c715ea02 | 17 | <li>Reference: <a href=''>0102638976</a></li> |
| 299a08f3 NR |
18 | <li>News link: <a href='https://tech.slashdot.org/story/18/09/06/1839242/google-investigating-issue-with-blurry-fonts-on-new-chrome-69'>https://tech.slashdot.org/story/18/09/06/1839242/google-investigating-issue-with-blurry-fonts-on-new-chrome-69</a></li> |
| 19 | <li>Source link: <a href='https://www.zdnet.com/article/google-investigating-issue-with-blurry-fonts-on-new-chrome-69/'>https://www.zdnet.com/article/google-investigating-issue-with-blurry-fonts-on-new-chrome-69/</a></li> | |
| 20 | </ul> | |
| 21 | <br/> | |
| 22 | <div class='content' style='text-align: justify'> | |
| e818d449 | 23 | Since the [1]release of Chrome 69 earlier this week , countless of users have gone on social media and Google Product Forums to [2]complain about "blurry" or "fuzzy" text inside Chrome . ZDNet:<br/><br/>> 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.<br/><br/>Some users have also expressed concerns over Chrome not showing [3]"trivial subdomains" including www and secure lock sign in the address bar.<br/><br/><br/><br/>[1] https://tech.slashdot.org/story/18/09/04/1711250/chrome-69-arrives-with-revamped-design-more-powerful-omnibox-and-better-password-manager<br/><br/>[2] https://www.zdnet.com/article/google-investigating-issue-with-blurry-fonts-on-new-chrome-69/<br/><br/>[3] https://bugs.chromium.org/p/chromium/issues/detail?id=881410 |
| 299a08f3 NR |
24 | </div> |
| 25 | <hr/> | |
| 26 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 27 | <h3>Whats the deal (Score:2)</h3> |
| 299a08f3 NR |
28 | <div class='by' style='font-style: italic;'>by 110010001000 ( 697113 )</div> |
| 29 | <div class='comment_content'><p></p><p>Whats the deal with the new interface. Looks like we are back to rounded corners again.</p></div> | |
| 30 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 31 | <h3></h3> |
| 299a08f3 NR |
32 | <div class='by' style='font-style: italic;'></div> |
| 33 | <div class='comment_content'></div> | |
| 34 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 35 | <h3>Re: (Score:1)</h3> |
| 299a08f3 NR |
36 | <div class='by' style='font-style: italic;'>by 110010001000 ( 697113 )</div> |
| 37 | <div class='comment_content'><p></p><p>And what's the deal with decaf coffee? How do they get the caffeine out of there, and then where does it go?</p></div> | |
| 38 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 39 | <h3>Re: (Score:1)</h3> |
| 299a08f3 NR |
40 | <div class='by' style='font-style: italic;'>by Anonymous Coward</div> |
| 41 | <div class='comment_content'><p></p><p>Why do they put caffeine in coffee and then take it back out?</p><p>And why if Chrome rendering fonts in the first place? That's a job for the operating system.</p></div> | |
| 42 | </div> | |
| 43 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 44 | <h3>Re: Whats the deal (Score:2)</h3> |
| 299a08f3 NR |
45 | <div class='by' style='font-style: italic;'>by spongman ( 182339 )</div> |
| 46 | <div class='comment_content'><p></p><p>dichloromethe (or ethyl acetate) leeching.</p></div> | |
| 47 | </div> | |
| 48 | </div> | |
| 49 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 50 | <h3>Re: (Score:2)</h3> |
| 299a08f3 NR |
51 | <div class='by' style='font-style: italic;'>by DontBeAMoran ( 4843879 )</div> |
| 52 | <div class='comment_content'><p></p><p>Score: 5, That's gold Jerry, GOLD!</p></div> | |
| 53 | </div> | |
| 54 | </div> | |
| 55 | </div> | |
| 56 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 57 | <h3>So Chrome 69 makes you blind? (Score:4, Funny)</h3> |
| 299a08f3 NR |
58 | <div class='by' style='font-style: italic;'>by the_skywise ( 189793 )</div> |
| 59 | <div class='comment_content'><p></p><p>The jokes write themselves...</p></div> | |
| 60 | </div> | |
| 61 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 62 | <h3>Blurry Fonts... (Score:2)</h3> |
| 299a08f3 NR |
63 | <div class='by' style='font-style: italic;'>by Oswald McWeany ( 2428506 )</div> |
| 64 | <div class='comment_content'><p></p><p>Maybe they need to put on their Google Glass so they can read the fonts clearer.</p></div> | |
| 65 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 66 | <h3>Re: (Score:3)</h3> |
| 299a08f3 NR |
67 | <div class='by' style='font-style: italic;'>by Z00L00K ( 682162 )</div> |
| 68 | <div class='comment_content'><p></p><p>They just started to use Cleartype and the fuzzy fonts.</p><p>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.</p></div> | |
| 69 | </div> | |
| 70 | </div> | |
| 71 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 72 | <h3>I bet you (Score:5, Insightful)</h3> |
| 299a08f3 NR |
73 | <div class='by' style='font-style: italic;'>by The MAZZTer ( 911996 )</div> |
| 74 | <div class='comment_content'><p></p><p>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.</p></div> | |
| 75 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 76 | <h3>Re: (Score:2)</h3> |
| 299a08f3 NR |
77 | <div class='by' style='font-style: italic;'>by omnichad ( 1198475 )</div> |
| 78 | <div class='comment_content'><p></p><p>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.</p></div> | |
| 79 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 80 | <h3></h3> |
| 299a08f3 NR |
81 | <div class='by' style='font-style: italic;'></div> |
| 82 | <div class='comment_content'></div> | |
| 83 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 84 | <h3>Re: (Score:2)</h3> |
| 299a08f3 NR |
85 | <div class='by' style='font-style: italic;'>by omnichad ( 1198475 )</div> |
| 86 | <div class='comment_content'><p></p><p>If it looks significantly worse, it could also have nothing at all to do with the bug - Chrome is DPI aware and should never have that enabled. Especially since the bug report doesn't have any mention of anything but the system DPI setting.</p></div> | |
| 87 | </div> | |
| 88 | </div> | |
| 89 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 90 | <h3></h3> |
| 299a08f3 NR |
91 | <div class='by' style='font-style: italic;'></div> |
| 92 | <div class='comment_content'></div> | |
| 93 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 94 | <h3>Re: (Score:2)</h3> |
| 299a08f3 NR |
95 | <div class='by' style='font-style: italic;'>by omnichad ( 1198475 )</div> |
| 96 | <div class='comment_content'><p></p><p>So you like the way I word it (No Giggity).</p></div> | |
| 97 | </div> | |
| 98 | </div> | |
| 99 | </div> | |
| 100 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 101 | <h3>Re: (Score:3)</h3> |
| 299a08f3 NR |
102 | <div class='by' style='font-style: italic;'>by Solandri ( 704621 )</div> |
| 103 | <div class='comment_content'><p></p><p>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.</p><p></p><p>Under the hood, there's also ClearType which runs on top of DPI scaling, and does [1]subpixel rendering [grc.com] (using the individual red, green, and blue subp</p><p></p><p></p><p></p><p></p><p>[1] https://www.grc.com/ctwhat.htm</p></div> | |
| 104 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 105 | <h3>Re: (Score:2)</h3> |
| 299a08f3 NR |
106 | <div class='by' style='font-style: italic;'>by omnichad ( 1198475 )</div> |
| 107 | <div class='comment_content'><p></p><p>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.</p></div> | |
| 108 | </div> | |
| 109 | </div> | |
| 110 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 111 | <h3>Re: (Score:2)</h3> |
| 299a08f3 NR |
112 | <div class='by' style='font-style: italic;'>by Scoth ( 879800 )</div> |
| 113 | <div class='comment_content'><p></p><p>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.</p></div> | |
| 114 | </div> | |
| 115 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 116 | <h3>Re: (Score:2)</h3> |
| 299a08f3 NR |
117 | <div class='by' style='font-style: italic;'>by Ingenium13 ( 162116 )</div> |
| 118 | <div class='comment_content'><p></p><p>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.</p></div> | |
| 119 | </div> | |
| 120 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 121 | <h3>Re: (Score:2)</h3> |
| 299a08f3 NR |
122 | <div class='by' style='font-style: italic;'>by greenwow ( 3635575 )</div> |
| 123 | <div class='comment_content'><p></p><p>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.</p></div> | |
| 124 | </div> | |
| 125 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 126 | <h3></h3> |
| 299a08f3 NR |
127 | <div class='by' style='font-style: italic;'></div> |
| 128 | <div class='comment_content'></div> | |
| 129 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 130 | <h3>Re: I bet you (Score:2)</h3> |
| 299a08f3 NR |
131 | <div class='by' style='font-style: italic;'>by spongman ( 182339 )</div> |
| 132 | <div class='comment_content'><p></p><p>They don't?</p></div> | |
| 133 | </div> | |
| 134 | </div> | |
| 135 | </div> | |
| 136 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 137 | <h3>Not new (Score:2)</h3> |
| 299a08f3 NR |
138 | <div class='by' style='font-style: italic;'>by Tailhook ( 98486 )</div> |
| 139 | <div class='comment_content'><p></p><p>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....</p></div> | |
| 140 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 141 | <h3>Re: (Score:1)</h3> |
| 299a08f3 NR |
142 | <div class='by' style='font-style: italic;'>by MidSpeck ( 1516577 )</div> |
| 143 | <div class='comment_content'><p></p><p>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.</p></div> | |
| 144 | </div> | |
| 145 | </div> | |
| 146 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 147 | <h3></h3> |
| 299a08f3 NR |
148 | <div class='by' style='font-style: italic;'></div> |
| 149 | <div class='comment_content'></div> | |
| 150 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 151 | <h3>Re: (Score:2)</h3> |
| 299a08f3 NR |
152 | <div class='by' style='font-style: italic;'>by Z34107 ( 925136 )</div> |
| 153 | <div class='comment_content'><p></p><p>Text wrapping is a "solved" problem, too, but you're still doing it by hand for some reason.</p></div> | |
| 154 | </div> | |
| 155 | </div> | |
| 156 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 157 | <h3>While they're at it (Score:2)</h3> |
| 299a08f3 NR |
158 | <div class='by' style='font-style: italic;'>by Pedestrianwolf ( 1591767 )</div> |
| 159 | <div class='comment_content'><p></p><p>..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.</p></div> | |
| 160 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 161 | <h3>Re: (Score:3)</h3> |
| 299a08f3 NR |
162 | <div class='by' style='font-style: italic;'>by ArchieBunker ( 132337 )</div> |
| 163 | <div class='comment_content'><p></p><p>Chrome has a major UI re-design? Firefox is going to be pulling some late nights to catch up!</p></div> | |
| 164 | </div> | |
| 165 | </div> | |
| 166 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 167 | <h3>It's also has performance regressions (Score:2)</h3> |
| 299a08f3 NR |
168 | <div class='by' style='font-style: italic;'>by Suren Enfiajyan ( 4600031 )</div> |
| 169 | <div class='comment_content'><p></p><p>On my Lenovo G570 the latest chrome also has very high CPU usage on [1]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.</p><p></p><p></p><p></p><p></p><p>[1] http://slither.io/</p></div> | |
| 170 | </div> | |
| 171 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 172 | <h3>BSOD (Score:2)</h3> |
| 299a08f3 NR |
173 | <div class='by' style='font-style: italic;'>by jimbrooking ( 1909170 )</div> |
| 174 | <div class='comment_content'><p></p><p>After installing ALL pages I visit are pure black. No text or graphics.</p></div> | |
| 175 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 176 | <h3>Re: (Score:2)</h3> |
| 299a08f3 NR |
177 | <div class='by' style='font-style: italic;'>by jimbrooking ( 1909170 )</div> |
| 178 | <div class='comment_content'><p></p><p>Fix (Win 7 Home): Uninstall Chrome, delete all browsing date. reinstall Chrome, be dazzled by the curviness.</p></div> | |
| 179 | </div> | |
| 180 | </div> | |
| 181 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 182 | <h3>Can someone summarize the linked article? (Score:4, Funny)</h3> |
| 299a08f3 NR |
183 | <div class='by' style='font-style: italic;'>by kaizendojo ( 956951 )</div> |
| 184 | <div class='comment_content'><p></p><p>I upgraded and I can't read it.</p></div> | |
| 185 | </div> | |
| 186 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 187 | <h3>See Jeff Probst ... (Score:2)</h3> |
| 299a08f3 NR |
188 | <div class='by' style='font-style: italic;'>by CaptainDork ( 3678879 )</div> |
| 189 | <div class='comment_content'><p></p><p>... about this.</p><p>I remember on Survivor®, back in the day, they had a "blurry tit," problem.</p><p>They fixed that by disallowing exposed tits.</p><p>Google should remove the tits from their fonts.</p></div> | |
| 190 | </div> | |
| 191 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 192 | <h3>trivial subdomain hiding (Score:2)</h3> |
| 299a08f3 NR |
193 | <div class='by' style='font-style: italic;'>by Zaiff Urgulbunger ( 591514 )</div> |
| 194 | <div class='comment_content'><p></p><p>So this "trivial subdomain hiding" thing... it's a crap idea right?</p></div> | |
| 195 | </div> | |
| 196 | <div class='comment' style='display: block; margin-left: 80px'> | |
| c715ea02 | 197 | <h3>Here's my take as a Mac user (Score:2)</h3> |
| 299a08f3 NR |
198 | <div class='by' style='font-style: italic;'>by DontBeAMoran ( 4843879 )</div> |
| 199 | <div class='comment_content'><p></p><p>First of all, I really hate these thin fonts. They may look neat on hi-DPI displays but not everyone has one.</p><p>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.</p></div> | |
| 200 | </div> | |
| 201 | </div> | |
| 202 | </body> |