Ayu

@LasseRosenow, I'm not very opposed to that actually. However, the original reason why the additional suffix was included was to help differentiate the font files to fit this [recommendation](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Fonts/Variable_Fonts_Guide#working_with_older_browsers) from...

It sounds like a reasonable idea, although I feel fairly uneasy to make it a default setting since I'm unsure how it will affect the tens of thousands of projects...

I actually agree with your points now that you mention those details. But now I recall why this is a very messy problem. We actually did previously serve VFs as...

> (Also, nowadays probably all [relevant browsers support `woff2`](https://caniuse.com/?search=woff2), so removing support for `woff` in general could be an option too.) I don't think that's an option as we still...

I do feel that offering developer flexibility is more favourable than restricting them if we don't know the various use cases. In the case of websites, I wouldn't recommend it,...

I can't necessarily change it now due to it being a breaking change. However, we could just append a duplicate of the same class with the "correct" CSS class name....

Yeah it's the default behaviour of the `font-display` property. We can only ship one as the default, and Google Lighthouse prefers the `swap` behaviour which gives you the FOUT behaviour....

> Any updates on the ability to the modify the default `font-display` property? Finishing #520 would enable #234 to be resolved quickly. That would be a possible solution. We're also...

No ETA. PRs are welcome if you want to help speed things up 🙂

It's definitely not intended. We added a generator for Material Icons a long long time ago since it needed that custom class, but it seems to have carried over to...