Add test for Slashdot + fix style
[gofetch.git] / test / expected / SLASHDOT / 0102638976.header
CommitLineData
299a08f3
NR
10Google Investigating Issue With Blurry Fonts on new Chrome 69 (zdnet.com) null/SLASHDOT/0102638976 70\r
2i Thursday September 06, 2018 @11:30PM (msmash)\r
3i from the blurry-texts dept.\r
4i\r
5i Since the release of Chrome 69 earlier this week, countless of\r
6i users have gone on social media and Google Product Forums to\r
7i complain about "blurry" or "fuzzy" text inside Chrome. ZDNet:\r
8i The blurred font issue isn't only limited to text rendered\r
9i inside a web page, users said, but also for the text\r
10i suggestions displayed inside the address bar search drop-down,\r
11i and Chrome's Developer Tools panel. [...] According to\r
12i reports, the issue only manifests for Chrome 69 users on\r
13i Windows. Those who rolled back to Chrome 68 stopped having\r
14i problems. Users said that changing Chrome, operating system,\r
15i or screen DPI settings didn't help. "Our team is investigating\r
16i reports of this behavior. You can find more information in\r
17i this public bug report," a Google spokesperson said last night\r
18i after first user complaints started surfacing online. Some\r
19i users have also expressed concerns over Chrome not showing\r
20i "trivial subdomains" including www and secure lock sign in the\r
21i address bar.\r
22i\r