Bug 214974 – [Wincairo] Some icons of FontAwesome icon set are not rendered

• Component: Layout and Rendering
• Status: NEW

[Thomas Brodt]

Created attachment 405580 [details]
a simple html file with three fontawesome icons

Some of the Fontawesome icons are not rendered with the current win cairo (32-bit) engine on Windows 10 (2004). Tested with Fontawesome 5.10.1 and 5.14.0.

For a test, take the MiniBrowser and open the attached html. You additionally need the fontawesome files (https://fontawesome.com/download).

It should show two pencil icons with a trash can inbetween. The trash can is not displayed. The trash can is one of the examples that don't get rendered, while others do.

[Fujii Hironori]

Created attachment 405624 [details]
[Screenshot] WinCairo port

"fal fa-trash-alt" is not included in Free version.
But, I can test both Pro and Free versions of it here.
https://fontawesome.com/icons?d=gallery&q=trash-alt

"fas fa-trash-alt" and "far fa-trash-alt" are Free, and also exhibiting the issue.

[Fujii Hironori]

Created attachment 405655 [details]
[Screenshot] notepad.exe showing fa-regular-400.ttf and fa-solid-900.ttf

Free version contains three fonts fa-brands-400, fa-regular-400 and fa-solid-900.
WebKit Windows ports can show fa-brands-400.woff2 and fa-solid-900.woff2, but fa-regular-400.woff2.

I installed fa-regular-400.ttf and fa-solid-900.ttf into my Windows 10.
Notepad.exe can show fa-solid-900.ttf, but fa-regular-400.ttf.

This seems that font issue. Windows doesn't like the fonts.

[Fujii Hironori]

Created attachment 405657 [details]
[Screenshot] Character Map of fa-regular-400.ttf

Windows has a useful app "Character Map" to show all glyphs in a installed font.
Only some glyphs of fa-regular-400.ttf can show.

[Fujii Hironori]

Created attachment 405658 [details]
[Screenshot] Fontforge of fa-regular-400.ttf

But, it has more. Fontforge (Linux) can show all glyphs of it.

[Fujii Hironori]

Even though legacy windows apps (WinCairo, notepad.exe, Character Map) can't render the glyphs, modern Windows apps (Chrome, Firefox, IE) can.
Can DirectWrite render the font?

[Thomas Brodt]

We only had issues with our "internal" wincairo based webkit. 

The regular external stand-alone browsers like Chrome, Firefox, Edge had no problem.

[Thomas Brodt]

Because the other browsers show all Fontawesome icons used in our application, I first thought it might be a wincairo issue. But I have the impression that it is rather a problem with the font files from fontawesome. 

Network traffic showed that the woff2 files were used, e.g. fa-light-300.woff2 in my case. Somehow the other browsers seem to get around errors in the font files.

An update from Fontawesome pro 5.10.1 to 5.14.0 makes more icons work for us, so there was a relevant change on the font files.

Still remains the effect that the minibrowser doesn't show all variants of an icon like the trash cans mentioned above on their own wep page. But the font delivery mechanism for the gallery on their web page seems different from the files deployed with an application like it is in our case. maybe that also plays into that.