Skip to content

Loading…

[Firefox] Local caching font issue (fonts.googleapis.com) #529

Closed
gitarra opened this Issue · 4 comments

2 participants

@gitarra

Tested with Firefox Nightly and Firefox Developer Edition.

When you enable µblock's experimental local caching feature the fonts stop working on this website.

µblock shows the requests as yellow but the fonts do not work on the pages.

I'm getting the following errors in the web console:

Local caching also seem to cause weirdness on CDNs covered by the HTTPS Everywhere addons rulesets but thats for another issue and time.

@gorhill

Works fine for me. Does it work if you disable HTTPS Everywhere?

@gitarra

This seems a bit tricky to trigger, it isnt related to HTTPS Everywhere I've just noticed some interesting behaviour with that addon and µblock local caching, but its another thing.

I tried to reproduce this again and was able to after some work, heres the steps I used:

Installed Firefox Developer Edition (cleaned profile). Installed µblock, enabled experimental features.
Restarted browser.
Went to the site, the fonts work fine. Navigated mindlessly around the site just clicking links around.
Restarted browser.
Navigated to the site again clicked a couple of links.
Restarted browser.
Now when I fired up Firefox this time and navigated to the site the fonts work no more.

When the fonts work there is only a single request to http://fonts.googleapis.com/css?family=Oswald:400,700|Roboto+Slab:400,700. Then the issue starts to manifest and there pops up requests to woff and woff2 files at fonts.gstatic.com, until the fonts stop working and there are repeated requests to fonts.gstatic.com, its like the page is trying to repeatedly load the fonts but fails and gives up.

Here is a screenshot showing the page with web console while having local caching disabled:
Web console and page with working fonts

Here is the web console and µblock request log when the fonts do not work:
Fonts broken web console
Fonts broken request log

@gitarra

Another site with the same issue: http://muropaketti.com/

Now I got how to reliably reproduce on a clean profile, it requires two browser restarts:

With experimental features enabled, visit the site. The fonts work, note only one request to fonts.googleapis.com.
Restart browser.
Visit the site, the fonts load a bit funky, flashing on and off, theres a few requests to fonts.gstatic.com now.
Restart browser.
Visit the site, fonts do not work. The amount of requests to the samel font files on fonts.gstatic.com at page load increases every browser restart.

@gorhill

Dup of #291.

@gorhill gorhill closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.