Wrong font rendering - very bad

[SylwesterZ]

Evident bug in font rendering is visible on Ghostery upgrade page:
https://www.wappalyzer.com/upgraded?v5.7.3

Even worse at 50%:

What should be seen - Firefox example:

50%:

Look at letter "e" and overall clarity, vertical antialiasing is simply wrong (looks like only horizontal AA was applied), Firefox is way, way better.

PS. On bigger zooms from 130% AA suddenly changes and You'll see proper rendering:

[SylwesterZ]

How could it be "broken" when properly displayed in Firefox/Windows - screens above?

[Pesala]

@SylwesterZ I also could not detect any difference, but said nothing because my vision is not sharp enough to detect minor differences.

Web fonts are cached locally after vising a web page that uses them. If you clear your cache in Firefox. you might see what we see.

[SylwesterZ]

Maybe your default font rendering mode in Firefox is wrong - on some systems default setting is simply ugly.
In Firefox's about:config set gfx.font_rendering.cleartype_params.rendering_mode to 5 to force proper font rendering.

[SylwesterZ]

You have wrong settings (why Firefox choose broken one on Your system is another question, on my systems i do not have to change it - it's good at default) and the same ugly rendering is on Chrome based browsers. This is fault of Vivaldi if choose to not fix it.

Font is working fine, open it in Photoshop or even install to Windows/Linux, it works fine. Blame wrong browser behaviour, not font - the same ugly rendering can be spot with different fonts, one i post is most evident.

PS. If You look deep, you will see that all letters has wrong outlines, not antialiases properly vertically - outlines are always snapped to pixel grid and this is wrong.

[SylwesterZ]

Another quick example, using very known Lato font:

Look at g letter outline, it is wrongly snapped to vertical grid, when it should be not, compare yourself outline at other sizes.
Chrome engine used by Vivaldi has wrong rendering and it need to be fixed. QED.

[Ayespy]

@SylwesterZ The website webfont is specified "Averta" family as detected by firefox. This is a font family which does not even exist on the vast majority of systems. The consequence is that, in Firefox and all other browsers on my machine for instance, no proper display font can be selected. All of my browsers, including Firefox, show that page exactly the same - crappy, muddy font.

Interestingly, unable to match the font class, all browsers copy that page without font attribute - which means that if I paste it into a document without specifying any font attribute, it pastes as whatever the default font is for the document I have set up - except in Firefox, which converts the pasted font attribute to Times New Roman, which is not the way the page is coded, and is not the default font for my document.

How you managed to make that page display like Arial in Firefox is anyone's guess. It won't do it here.

[Ayespy]

@SylwesterZ Sorry for your trouble. For the time being, Vivaldi will not be interfering with how the Blink engine renders font. The amount of code necessary would take too much time and resources away from the planned development of the browser. It's a known situation that Blink renders some fonts in ways that some users find unacceptable - but it's not something Vivaldi can address right now.

[SylwesterZ]

Are You talking about font substitution? There is no font substitution and used Averta font is displayed using CSS @font-face.
I hoped that Vivaldi developers could fix engine bugs and shortcomings, and maybe it will at some point...

[Ayespy]

@SylwesterZ At some point. It's early days yet.

[SylwesterZ]

Thanks for help, have a nice day