Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

تلاش سپورٹ

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.

مزید سیکھیں

اس تھریڈ کو آرکائیوکیا گیا تھا۔ اگر آپ کو مدد کی ضرورت ہو تو براہ مہربانی نیا سوال پوچھیں۔

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

  • 1 جواب دیں
  • 0 میں یہ مسئلہ ہے
  • 165 دیکھیں
  • آخری جواب بذریعہ 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?

منتخب شدہ حل

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

اس جواب کو سیاق و سباق میں پڑھیں 👍 0

تمام جوابات (1)

Filcuk
Filcuk سوال کا مالک
more options

منتخب شدہ حل

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