3 ms·

This seems to be an issue with the Google Fonts API, not Firefox itself. For me (Firefox 100, Arch Linux) all the options work fine on https://v-fonts.com/font

This seems to be an issue with the Google Fonts API, not Firefox itself. For me (Firefox 100, Arch Linux) all the options work fine on https://v-fonts.com/fonts/roboto-flex https://v-fonts.com/fonts/roboto-flex (all of them have _some_ effect, have smooth transitions, and look roughly the same as in Chromium), but on https://fonts.google.com/specimen/Roboto+Flex?query=roboto#type-tester https://fonts.google.com/specimen/Roboto+Flex?query=roboto#t... the only option that does anything is Weight, and that one only snaps into one of three broad categories.

wildrhythms 4y ago
It's a Windows Directwrite bug - https://twitter.com/googlefonts/status/1522775267852181504?s=20&t=mkkR5H9H6nb_CYDxVKJLEQ https://twitter.com/googlefonts/status/1522775267852181504?s...
- Nullabillity 4y ago
  No, it's a GFonts bug that they're overly eager to work around a DW bug, even if the system doesn't even have DW installed.
runarberg 4y ago
I recently incorporated a variable font into a web app at $WORK (as in less then 6 months ago). And I remember seeing some issues like that Using google hosted variable fonts just didn’t seem to work in firefox. There was something about defining the range in the @font-face rule which google font omits (or does differently), or how variable fonts are consumed (font-weight vs font-variation-settings). My conclusion was—if my memory is accurate—that there was no way we could use google hosted fonts (you should always self host your fonts anyway if you can) and you needed split files for italics (the italic axis simply doesn’t work consistently across browsers). EDIT: Here is an article describing the current state of the italics axis in browsers: https://rwt.io/typography-tips/getting-bent-current-state-italics-variable-font-support https://rwt.io/typography-tips/getting-bent-current-state-it...

wildrhythms 4y ago

It's a Windows Directwrite bug - https://twitter.com/googlefonts/status/1522775267852181504?s=20&t=mkkR5H9H6nb_CYDxVKJLEQ https://twitter.com/googlefonts/status/1522775267852181504?s...

Nullabillity 4y ago
No, it's a GFonts bug that they're overly eager to work around a DW bug, even if the system doesn't even have DW installed.

runarberg 4y ago

I recently incorporated a variable font into a web app at $WORK (as in less then 6 months ago). And I remember seeing some issues like that Using google hosted variable fonts just didn’t seem to work in firefox. There was something about defining the range in the @font-face rule which google font omits (or does differently), or how variable fonts are consumed (font-weight vs font-variation-settings). My conclusion was—if my memory is accurate—that there was no way we could use google hosted fonts (you should always self host your fonts anyway if you can) and you needed split files for italics (the italic axis simply doesn’t work consistently across browsers). EDIT: Here is an article describing the current state of the italics axis in browsers: https://rwt.io/typography-tips/getting-bent-current-state-italics-variable-font-support https://rwt.io/typography-tips/getting-bent-current-state-it...