Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

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

  • 1 Antwort
  • 0 haben dieses Problem
  • 1 Aufruf
  • Letzte Antwort von 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?

Ausgewählte Lösung

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

Diese Antwort im Kontext lesen 👍 0

Alle Antworten (1)

Filcuk
Filcuk Fragesteller
more options

Ausgewählte Lösung

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