Add test for Slashdot + fix style

[gofetch.git] / test / expected / SLASHDOT / 0102638976.header

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