BTW, isn't this very similar to turning off the option in Firefox browsers to use fonts set by the website, if available? Either way, depending on one's tastes, the website may lose a bit of its personality then, at least on typical Chromium browser on Windows, fallback fonts still lack that extra touch that can be achieved following system parameters. Some fonts look worse than others when rendered the Chromium default Windows way and really do cause eye strain for me, though Clean Font Families, which out some time ago, can help a bit. Edge with edge://flags/#edge-enhance-text-contrast flag enabled is the exception. Chromium browsers on Linux apparently do follow system settings, so nothing out of the ordinary here (ignoring possible exceptions with niche distros/desktop environments).īut they apparently, at least from outsider perspective, use hardcoded parameters on Windows. So it's nothing to do with fonts (maybe certain types of fonts are exception, but I wouldn't know for certain), just how they're rendered. Turned it off to see what it's like and holy crap, hell no, can't imagine using that setting on regular basis.

I looked through System settings on Manjaro KDE and font anti-aliasing is enabled by default.

Ublock chromium edge