RenderingNG: An architecture that makes and keeps Chrome fast for the long term

Re:RenderingNG: An architecture that makes and keeps Chrome ... by maskros on Thursday October 07, 2021 @07:40AM (#28784970)

Rendering fast is nice, but when are they going to make the rendering look good? Image scaling at non-integer scales in Chrome is atrocious -- either coming out a blurry or aliased mess.

I almost always need to zoom in 20% to 50% because web designers love tiny fonts too much, and setting a minimum font size breaks their fancy layouts. This results in Chrome making a mess of all images on the page.

Thankfully Firefox resamples images so they look good at non-integer scaling factors too.

[ Parent | on HN ]

Re:RenderingNG: An architecture that makes and keeps Chrome ... by jd3 on Thursday October 07, 2021 @12:02PM (#28788101)

This is only tangentially related (images vs fonts), but a small pet peeve of mine that kept me from migrating to Chrome from Firefox on my Windows machine back in the day is the fact that Chrome uses an internal text antialiasing engine that is, as far as I can tell, impossible to disable. Firefox, on the other hand, honors the system antialiasing settings.

So, for example, if you disable cleartype on Windows, you will have crisp aliased fonts at default font sizes on Firefox, but you will still get blurry antialiased fonts in Chrome no matter what.

[ Parent | on HN ]

Re:RenderingNG: An architecture that makes and keeps Chrome ... by chrishtr on Thursday October 07, 2021 @08:24PM (#28794011)

(blog post author here)

Could you file a bug with an example at crbug.com/new?

[ Parent | on HN ]