page doesn't refresh while developer tools are open
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: luca, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:81.0) Gecko/20100101 Firefox/81.0
Steps to reproduce:
Open a page
Open developer tools
Edit some css and upload the updated file to the server
Refresh the page
Actual results:
The page is refreshed but the new css is not applied to the page, I still see the page with the old css.
Also, in the developer tools the old css is showed.
To see the correct page I have to close the developer tools and press ctrl+F5
The same problem occurred in Firefox 80 and probably 79
Expected results:
I should see the page with the new css applied, and the new css should be reflected in the developer tools.
|
||
Updated•5 years ago
|
|
||
Comment 1•5 years ago
|
||
Probably the old css is from cache
Could you make sure all cache control headers are correct?
Another question: if dev tools is closed, can you see the correct css file?
(In reply to Kershaw Chang [:kershaw] from comment #1)
Probably the old css is from cache
Probably, I don't know...
Could you make sure all cache control headers are correct?
I suppose they are, it happens in different sites and a couple firefox releases ago that didn't happen, I have no reason to believe the are not correct.
Another question: if dev tools is closed, can you see the correct css file?
If the dev tools are open I can press F5, ctrl+F5, clear all cache, but the new css is never loaded (or applied, I don't know).
I have to close dev tools, then if I press ctrl+F5 the page is refreshed correctly with the new css
|
|
||
Comment 3•5 years ago
|
||
(In reply to XXVII from comment #2)
(In reply to Kershaw Chang [:kershaw] from comment #1)
Probably the old css is from cache
Probably, I don't know...Could you make sure all cache control headers are correct?
I suppose they are, it happens in different sites and a couple firefox releases ago that didn't happen, I have no reason to believe the are not correct.
Could you try to use mozregression to help us find out the problem?
Thanks.
|
|
||
Comment 4•4 years ago
|
||
Close because we don't have enough information.
Description
•