This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Firefox doesn't reload CSS added through @import while using CTRL+Shift+R

  • 1 baphendule
  • 0 zinale nkinga
  • 1 view
  • Igcine ukuphendulwa ngu Filcuk

Filcuk
Filcuk
more options

When refreshing and clearing cache using CTRL+Shift+R, browser should reload all assets. However when refreshing site with @import(ed) style sheet, it does not update.

The workaround is to open the style sheet in a new tab (e.g. https://my.web.com/assets/custom.css) and run refresh + clear cache there CTRL+Shift+R, which loads the updated style sheet.

Then, upon refreshing the original site (https://my.web.com), the CSS has been updated.


Is this a bug or expected behaviour?

When refreshing and clearing cache using CTRL+Shift+R, browser should reload all assets. However when refreshing site with @import(ed) style sheet, it does not update. The workaround is to open the style sheet in a new tab (e.g. https://my.web.com/assets/custom.css) and run refresh + clear cache there CTRL+Shift+R, which loads the updated style sheet. Then, upon refreshing the original site (https://my.web.com), the CSS has been updated. Is this a bug or expected behaviour?

Isisombululo esikhethiwe

After further testing, I've discovered this was due to Cloudflare caching, NOT Firefox - my apologies.

Funda le mpendulo ngokuhambisana nalesi sihloko 👍 0

All Replies (1)

Filcuk
Filcuk Umnikazi wombuzo
more options

Isisombululo Esikhethiwe

After further testing, I've discovered this was due to Cloudflare caching, NOT Firefox - my apologies.