4 ms·

That's not Chrome, it's Firefox. Looks the same on my machine as well, all jaggedy. I'm using FF 36. Let me go update and see if there's a difference... No dif

That's not Chrome, it's Firefox. Looks the same on my machine as well, all jaggedy. I'm using FF 36. Let me go update and see if there's a difference... No difference on 37. They just look terrible. http://i.imgur.com/exrS0u9.png http://i.imgur.com/exrS0u9.png EDIT: Wow, looks like turning ClearType OFF makes the font icons look much better: http://i.imgur.com/dwwagZN.png http://i.imgur.com/dwwagZN.png Interesting.

dandelany 11y ago
Wow. I can't believe it's 2015 and both Chrome and Firefox are still battling text antialiasing bugs.
- idbehold 11y ago
  I think you mean battling Microsoft's terrible text antialiasing.
- JohnTHaller 11y ago
  It's likely an issue with buggy video drivers. Firefox has a database of drivers on a blacklist that will crash due to instability. When it detects them in use, it will disable hardware acceleration which decreases performance and quality of some things like font rendering. Judging by the earlier screenshot, this is on a lower end laptop at 1366x768 resolution with an integrated graphics card. Most laptop makers never update the bundled drivers to fix bugs even though Intel and AMD regularly update the drivers of their integrated graphics tech. So, users are stuck with an outdated buggy driver and no way to update it. Mozilla at least ensures that it won't crash.
  - milankragujevic 11y ago
    My screenshot is from a PC with AMD A10-7850K with integrated Radeon R7 graphics. I always download the latest AMD drivers and check for updates every month.
    - JohnTHaller 11y ago
      Here are the AMD drivers that are blacklisted: https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers#AMD.2FATI_cards https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drive...