All tests were made without any active extensions.
I couldnât observe the behavior in Firefox.
To get rid of the error, it might suffice to remove the wrapping url(...).Edit: Wrong conclusion. When the CSS is inlined and the (quoted) import URL contains a raw semicolon, then Chrome will treat this as the end of the statement and treat the URL up to the semicolon (including the url(" prefix) as relative URL.
So! As youâve researched, this is a known issue that Iâve been consciously ignoring since it still ends up requesting the correct resource directly after. It:
is in Chrome only (not in Safari nor Firefox)
due to the @import âŚ; in a <style> tag on the page (doesnât happen without the semicolon and doesnât happen from a css file either <link>ed or @importâed)
Iâve been hoping Chrome would fix this, but I was also considering un-inlining the worker css back to its own file, which would also fix this.
This was a change I introduced recently in moving our Source Serif Pro self-hosting to Google fonts. The immediate benefits of the Google-hosted version are smaller font files for most cases (they break up the fontâs unicode ranges across files) and the thumbnailerâs kerning used to be pretty awkward, but is now correct.