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

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Learn More

Esta discussão foi arquivada. Se precisar de ajuda, por favor, coloque uma nova questão.

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

  • 1 resposta
  • 0 têm este problema
  • 1 visualização
  • Última resposta por 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?

Solução escolhida

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

Ler esta resposta no contexto 👍 0

Todas as respostas (1)

Filcuk
Filcuk Proprietário da pergunta
more options

Solução escolhida

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