Closed ghost closed 3 years ago
I've tried to recreate your test case by downloading some version of font-awesome and bootstrap. I don't get exactly the same result as you, but I see the creation of the JavaScript-based preload polyfill produce another broken result. I think I see what the problem is, but it looks like it needs to be rewritten to be able to match things up correctly.
In the mean time, could you use subfont --browsers 'chrome>=50'
to disable it?
Fixed in 5.2.5 😌
Thanks a lot!
Subfont version: 5.2.3.
Subfont command:
subfont index.html -o ./ -r
initial index.html
initial about.html
result index.html
result about.html (here's the problem)
As you can see subfont generated a preload script the font families of which do not match the correct font url:
resulting about.html
In this case it matched font awesome with the Alice subset font file.
It also created two fallback font files (one for font awesome and the other for Alice font) and I' not sure that's the desired outcome because of the additional requests. How can I get subfont to generate one fallback file only?
resulting about.html
As you can see subfont generated fallback files
fallback-e995debd67.css
andfallback-94148c0c6e.css
.subfont command output: