Bugzilla

So it sounds like the web content (or rather, the font?) is relying on Chrome's particular choice of "character-not-found" fallback behavior, essentially (and getting broken output in Firefox and Safari as a result).

jfkthame, should we close this as INVALID?

Also, would you be willing to report this to FontAwesome (maybe at https://github.com/FortAwesome/Font-Awesome/issues ), to let them know they're doing something iffy by including a `.notdef` glyph and expecting it to be renderable?  I could do so but you can probably express the issue & answer any followup questions better than I could. :)

It looks like this exact WOFF file exists in their up-to-date public github repo, links below:

current tip:
https://github.com/FortAwesome/font-awesome-sass/blob/master/assets/fonts/font-awesome/fa-brands-400.woff2
perma-link:
https://github.com/FortAwesome/font-awesome-sass/blob/da54d68de6492cf173c616a1b3cb2ae660f03c91/assets/fonts/font-awesome/fa-brands-400.woff2

(this^ has the same md5sum as the version hosted on the affected site which I attached here as an attachment.)

There may not be much we can do about folks who have already downloaded & are using that woff file on their sites, but perhaps it'd be worth getting it fixed upstream to avoid this issue spreading.

So it sounds like the web content (or rather, the font?) is relying on Chrome's particular choice of "character-not-found" fallback behavior, essentially (and getting broken output in Firefox and Safari as a result).

jfkthame, should we close this as INVALID?

Also, would you be willing to report this to FontAwesome (maybe at https://github.com/FortAwesome/Font-Awesome/issues ), to let them know they're doing something iffy by including a `.notdef` glyph and expecting it to be renderable?  I could do so but you can probably express the issue & answer any followup questions better than I could. :)

It looks like this exact WOFF file exists in their up-to-date public github repo, links below:

current tip:
https://github.com/FortAwesome/font-awesome-sass/blob/master/assets/fonts/font-awesome/fa-brands-400.woff2
perma-link:
https://github.com/FortAwesome/font-awesome-sass/blob/da54d68de6492cf173c616a1b3cb2ae660f03c91/assets/fonts/font-awesome/fa-brands-400.woff2

(this^ has the same md5sum as the version hosted on the affected site which I attached here as an attachment, so presumably it's the same file and causes the same interop issue if someone tries to use its `.notdef` github glyph)

There may not be much we can do about folks who have already downloaded & are using that woff file on their sites, but perhaps it'd be worth getting it fixed upstream to avoid this issue spreading.