1605719 - Cache issue while developing

Status: UNCONFIRMED

(Core :: DOM: Navigation, defect, P4)

Description

[fabrice salvaire]

User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0

Steps to reproduce:

While developing a Sass stylesheet on Dango CMS ...

Actual results:

I get on some occasions an old css.

All cache features are disabled on the server side and a wget test give the right file. Thus the issue should not arise from the server side.

However the file transfer show "cached" on the network tab. ** Despite the "disable cache" checkbox is cached on the developer tab. **

I can reproduce the issue by opening the file in a new tab. Then I have to click on reload on the developer tab to get the right file. And to fix the issue I have to drop the Firefox cache manually.

Expected results:

Why there no simple way ??? Like the option to disable cache in a tab.

Comment 1

[fabrice salvaire]

typo: checkbox is checked

Comment 2

[Francesco Lodolo [:flod]]

There's a Disable HTTP cache setting in DevTools
https://developer.mozilla.org/en-US/docs/Tools/Settings

Also, CTRL+F5 should override the existing cache.

Comment 3

[fabrice salvaire]

This setting is connected to the one in the network tab, which is ** checked ** in my case. Thus the cache should be disabled. This setting seems to be only applied in some particular case, like a reload from the network table.

In addition, even with BrowserSync acting as a proxy, I observe woodoo behaviours, for example I obtained a refresh of the page with an old css just after unchecking a setting in the css editor (inspector tab) ...

Globally I have a bad experience with Firefox for web developments due to many woodoo behaviours.

Comment 4

[Clara Guerrero ( Need Info Brindusa Tot Please)]

Hi Fabrice,

To force fetching all content fresh all the time including images, resources such as style sheet etc. to facilitate this you can do the following:

1- Open a new window or tab in Firefox.
2- Type about:config in the address bar.
3- Search for “cache” in the search bar and look for network.http.use-cache in the filtered results.
4- Double-click it will toggle it from “true” to “false”. Default should be “true”.

Let me know if that works!

Best regards, Clara.

Comment 5

[Clara Guerrero ( Need Info Brindusa Tot Please)]

Hi Fabrice, did you have time to see my last message?

Best,
Clara