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

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

Learn More

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

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

  • 1 réponse
  • 0 a ce problème
  • 1 vue
  • Dernière réponse par 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?

Solution choisie

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

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (1)

Filcuk
Filcuk Auteur de la question
more options

Solution choisie

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