Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#56980 - [chromium] broken subpixel rendering since 63.0.3239.108-2

Attached to Project: Arch Linux
Opened by Marcoen Hirschberg (markun) - Saturday, 06 January 2018, 21:43 GMT
Last edited by Evangelos Foutras (foutrelis) - Sunday, 07 January 2018, 09:37 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Starting with chromium 63.0.3239.108-2, there seems to be no LCD text antialiasing in chromium. The result is more blurry text.

Additional info:

Noticed in: chromium 63.0.3239.132-1

I did some bisecting using arch linux package archives:

Last package without this issue: chromium 62.0.3202.94-2
First packge with this issue: chromium 63.0.3239.108-2

The google-chrome package 63.0.3239.132-1 does not have this issue and correctly shows LCD text antialiasing.

Steps to reproduce:

1) Open any page with black text on white background with "LCD text antialiasing".
2) Zoom in with "xmag" on the text.

The antialiasing should be done with different colors, but in the latest builds it is only grayscale, resulting in blurry text. See the attached (zoomed in) images.
   chromium-antialiasing-63.0.32... (5.8 KiB)
   chromium-antialiasing-62.0.32... (5.6 KiB)
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Sunday, 07 January 2018, 09:37 GMT
Reason for closing:  Fixed
Additional comments about closing:  chromium 63.0.3239.132-2
Comment by Evangelos Foutras (foutrelis) - Sunday, 07 January 2018, 07:21 GMT
Please test chromium 63.0.3239.132-2.
Comment by Marcoen Hirschberg (markun) - Sunday, 07 January 2018, 09:34 GMT
It's works, thanks for the quick fix!

Loading...