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-header'> | |
| c715ea02 | 12 | <h2><a href='0102638976.html'>Google Investigating Issue With Blurry Fonts on new Chrome 69 (zdnet.com)</a></h2> |
| 299a08f3 NR |
13 | <div class='details'>(Thursday September 06, 2018 @11:30PM (msmash) |
| 14 | from the blurry-texts dept.)</div> | |
| 15 | <br/> | |
| 16 | <div class='content' style='text-align: justify'> | |
| 17 | Since the release of Chrome 69 earlier this week, countless of users have gone on social media and Google Product Forums to complain about "blurry" or "fuzzy" text inside Chrome. ZDNet: 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. Some users have also expressed concerns over Chrome not showing "trivial subdomains" including www and secure lock sign in the address bar. | |
| 18 | </div> | |
| 19 | <hr/> | |
| 20 | </div> | |
| 21 | </body> |