Re:Brave Improves Its Ad-Blocker Performance with New Engine...
by mmmrk on Thursday June 27, 2019 @08:02AM
(#20293642)
What do you mean by ugly? That GDI text rendering is used on Windows instead of DirectWrite for some font families? This can be disabled in about:config by assigning `gfx.font_rendering.cleartype_params.force_gdi_classic_for_families` an empty value. Or do you mean that there's no subpixel positioning on non-Windows/macOS? That one has no fix, except when the text rendering part of WebRender goes into production.
[ Parent
| on HN ]
Re:Brave Improves Its Ad-Blocker Performance with New Engine...
by bscphil on Thursday June 27, 2019 @05:51PM
(#20299209)
I'm confused. Doesn't Firefox use Freetype on Linux? Freetype has subpixel rendering.
Re:Brave Improves Its Ad-Blocker Performance with New Engine...
by mmmrk on Friday June 28, 2019 @06:27PM
(#20309310)
Subpixel rendering is different from subpixel positioning.
See e.g. https://bugs.chromium.org/p/chromium/issues/detail?id=824153 for some gory details.
Re:Brave Improves Its Ad-Blocker Performance with New Engine...
by ahartmetz on Friday June 28, 2019 @10:13AM
(#20304450)
AFAICT Firefox text rendering has always been fine on Linux. Chrome until a year or two ago had no subpixel antialiasing, different gamma for antialiasing, or whatever - its text rendering used to look ugly, or more neutrally: different from everything else.