Hi mt3ch

This forum is focused on user questions; for developer questions please ask on Stack Overflow and tag it firefox

• https://stackoverflow.com/questions/tagged/firefox

Cheers!

...Roland

You can try these steps in case of issues with web pages:

You can reload web page(s) and bypass the cache to refresh possibly outdated or corrupted files.

• hold down the Shift key and left-click the Reload button
• press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
• press "Command + Shift + R" (Mac)

Clear the Cache and remove the Cookies for websites that cause problems via the "3-bar" Firefox menu button (Options/Preferences).

"Remove the Cookies" for websites that cause problems:

• Options/Preferences -> Privacy & Security
  Cookies and Site Data: "Manage Data"

"Clear the Cache":

• Options/Preferences -> Privacy & Security
  Cookies and Site Data -> Clear Data -> Cached Web Content: Clear

Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration is causing the problem.

• switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
• do NOT click the "Refresh Firefox" button on the Safe Mode start window

• https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
• https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems

Edit: Duplicate post

Hi mt3ch This forum is focused on user questions; for developer questions please ask on Stack Overflow and tag it firefox

• https://stackoverflow.com/questions/tagged/firefox

Cheers! ...Roland

Hi Roland

This is a browser issue not a developer issue. Stack Overflow won't help with browser bugs/issues.

Thanks.

You can try these steps in case of issues with web pages: You can reload web page(s) and bypass the cache to refresh possibly outdated or corrupted files.

• hold down the Shift key and left-click the Reload button
• press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
• press "Command + Shift + R" (Mac)

This resolved the problem (although for some reason clearing the cache from the menu options didn't) and it doesn't seem to be happening again for now.

Perhaps after some time of using the browser the cache is becoming corrupted or unreliable.

If it happens again, or too often, I will file a bug report.

Thanks.

This is definitely a user issue. Responding that it is a dev issue is basically telling me (and others) that we need to tell our users to shift refresh when css changes were made. Having a developer do that is fine. Having a user community do it is an issue.

Firefox 79 is more aggressive about caching CSS and a normal reload may not be suffiecient.

• https://wiki.developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/79#CSS

You can try these steps in case of issues with web pages: You can reload web page(s) and bypass the cache to refresh possibly outdated or corrupted files.

• hold down the Shift key and left-click the Reload button
• press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
• press "Command + Shift + R" (Mac)

Clear the Cache and remove the Cookies for websites that cause problems via the "3-bar" Firefox menu button (Options/Preferences). "Remove the Cookies" for websites that cause problems:

• Options/Preferences -> Privacy & Security
  Cookies and Site Data: "Manage Data"

"Clear the Cache":

• Options/Preferences -> Privacy & Security
  Cookies and Site Data -> Clear Data -> Cached Web Content: Clear

Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration is causing the problem.

• switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
• do NOT click the "Refresh Firefox" button on the Safe Mode start window

• https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
• https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems

This doesn't work for me at all. I still get the cached CSS. Even in safe mode. I'll have to investigate further when I have time, but this sort of bug should never have got past the censor.