← Back to context

Comment by california-og

19 hours ago

Most likely because your JS blocker also blocks custom fonts. It works fine without JS.

It does not: with JS blocked, the stylesheet for the webfont never gets injected. Even though it shouldn't need injecting in the first place.

  • I'm 100% sure it does. Check again.

    • Then you need to curl the URL, pipe it to an .html file, and then search the resulting file for "@font-face". The only place that has the @font-face rule for this fancy font is inside <template> syntax, meaning it will do nothing (template content is inert) until JS clones that template into the DOM as active content.

      3 replies →