Bugzilla

(In reply to Jonathan Kew [:jfkthame] from comment #5)
> Their family name, as provided in the `name` table of the font resources, is "Source Sans Pro". That's what Firefox recognizes: it scans the installed fonts and collects all the available family names.

(that said,  "Source Sans Pro" was renamed to "Source Sans <version>" or something like that)

> However, it seems that in Android they've decided to ignore the font family name provided by the font resources, and instead enumerate fonts using a sort of fontconfig-like XML file that exposes a *different* family name.

I run into this issues several times over the years before I fond that fonts.xml file. I tend to forget those details, from my memory:
*  `courier`  gets an courier-like font with Chromium. Firefox needs `cutive mono`. 
* `cursive` gets something expected on Chromium, Firefox needs `Dancing Script` (found this by accident months later). 
* Especially audacious is casual / Coming Soon. They minted a new generic family.
* Yesterday found: `font-family: sans-serif; font-stretch: condensed;` works with Firefox. Chromium ignores font-stretch and needs `font-family: sans-serif-condensed`.

> I suppose for compatibility, we should probably try to handle this (and other) font "aliases" that Android is using, but it makes me sad.

Are this bugs in Android or in Chromium/Blink? (not that there is any hope they would change that)

(In reply to Jonathan Kew [:jfkthame] from comment #5)
> Their family name, as provided in the `name` table of the font resources, is "Source Sans Pro". That's what Firefox recognizes: it scans the installed fonts and collects all the available family names.

(that said,  "Source Sans Pro" was renamed to "Source Sans <version>" or something like that)

> However, it seems that in Android they've decided to ignore the font family name provided by the font resources, and instead enumerate fonts using a sort of fontconfig-like XML file that exposes a *different* family name.

I run into this issues several times over the years before I fond that XML files. I tend to forget those details, from my memory:
*  `courier`  gets an courier-like font with Chromium. Firefox needs `cutive mono`. 
* `cursive` gets something expected on Chromium, Firefox needs `Dancing Script` (found this by accident months later). 
* Especially audacious is `casual` / `Coming Soon`. They minted a new generic family.
* Yesterday found and instantly used: `font-family: sans-serif; font-stretch: condensed;` works with Firefox. Chromium ignores font-stretch and needs `font-family: sans-serif-condensed`.

> I suppose for compatibility, we should probably try to handle this (and other) font "aliases" that Android is using, but it makes me sad.

Are this bugs in Android or in Chromium/Blink? (not that there is any hope they would change that)