Changes in source file not visible in debugger on reload
Categories
(DevTools :: Debugger, defect, P2)
Tracking
(Not tracked)
People
(Reporter: till, Assigned: bhackett1024)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [debugger-reserve])
Attachments
(1 file)
448 bytes,
text/html
|
Details |
Comment 1•10 years ago
|
||
Comment 2•10 years ago
|
||
Comment 3•7 years ago
|
||
Updated•7 years ago
|
Updated•6 years ago
|
Comment 5•6 years ago
•
|
||
I can still reproduce the problem using STR (and test case) from comment #2
Some more comments
- Disable cache in the Network panel seems to help.
- The problem seems to be in Private window only.
Honza
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Updated•6 years ago
|
Assignee | ||
Comment 6•6 years ago
|
||
I can reproduce this, and it should be fixed by bug 1538056, at least when reloading the tab while the debugger is open.
From the console.log() calls made it is clear that the current version of the page is running, and that the debugger is showing an outdated version of the HTML. The problem is that the debugger makes its own fetch to get the HTML, and it is getting stale contents. That fetch uses the browser's cache when possible (so that loading the source in the debugger doesn't have to incur overhead by going out to the network again). Presumably, when private browsing is on the browser cache is not updated with the new page contents --- then someone could see what happened while doing the private browsing --- and we wouldn't want to clear entries from the browser cache while private browsing for the same reason. If the debugger is operating a window that is in private browsing mode then it could avoid going to the cache, I guess, but bug 1538056 offers a way around the fetch call entirely. The HTML that is read off the network is used directly, and is guaranteed to be correct. This only applies when the page is loaded/reloaded with the debugger open, though.
Updated•6 years ago
|
Comment 7•5 years ago
|
||
This was fixed via bug 1538056.
Comment 8•5 years ago
|
||
oops, updated the wrong bug.
Comment 9•5 years ago
|
||
(In reply to Brian Hackett (:bhackett) from comment #6)
This only applies when the page is loaded/reloaded with the debugger open, though.
I can't reproduce this bug anymore and it seems to be fixed for me.
What do you mean by "when the page is loaded/reloaded with the debugger open"?
I tried to select another DevTools panel and reload and switch back to the Debugger, but it seems to be working.
Honza
Assignee | ||
Comment 10•5 years ago
|
||
(In reply to Jan Honza Odvarko [:Honza] (always need-info? me) from comment #9)
(In reply to Brian Hackett (:bhackett) from comment #6)
This only applies when the page is loaded/reloaded with the debugger open, though.
I can't reproduce this bug anymore and it seems to be fixed for me.
What do you mean by "when the page is loaded/reloaded with the debugger open"?
I tried to select another DevTools panel and reload and switch back to the Debugger, but it seems to be working.Honza
Oops, I should have said that other panels besides the debugger will work as well. When the devtools are open and attached to a tab, they mark the tab's docshell as being watched by the devtools, which causes streamed HTML associated with the tab to be sent to the devtools, so that the HTML does not need to be refetched when the debugger shows the source. The latter logic was added by bug 1538056, which per comment 6 should fix the underlying issue in this bug. Since you can't reproduce this bug anymore, that confirms this is fixed.
Comment 11•4 years ago
|
||
i can confirm that this bug is present in latest 85.0 version.
Comment 12•3 years ago
|
||
I can confirm this happens with 101.0.1 (64-bit). I have to use Edge as a workaround for the moment.
Description
•