Closed Bug 1157805 Opened 9 years ago Closed 7 years ago

Cannot refresh source maps from debugger

Categories

(DevTools :: Debugger, defect)

37 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: victor, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0
Build ID: 20150402191859

Steps to reproduce:

Step 1: on a page which includes `script.min.js`, I opened the debugger and viewed the original non-minified source (taken from `script.js` using source mapping). 

Step 2: add `alert("HI")` to `script.js` and generate `script.min.js`.

Step 3: refresh the page, ensure that "HI" is displayed.  

Step 4: view the non-minified source of `script.min.js` in the debugger again.


Actual results:

Debugger displays old version of `script.js`, without `alert("HI")` statement.

Ctrl+R and F5 do not load the new version of `script.js`. 

The following solution candidates also do not cause the debugger to display the new version of `script.js`: 

 - closing and reopening the "Debugger" tab
 - closing and reopening the developer tools
 - closing and reopening the tab where the site is displayed

The only solution I have found is to open a new tab and visit `http://localhost/script.js` (which displays the new version). 



Expected results:

I expected the debugger to display the new version of `script.js` (including the `alert("HI")` statement). Failing that, I would have expected either F5 or Ctrl-R to force a refresh and display the new version.
Same problem occurs in Firefox Developer Edition 39.0a2
Component: Untriaged → Developer Tools: Debugger
Still seems to be a bug.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Blocks: source-maps
I fixed this for other uses of the client-side service in bug 1366062.
I didn't debug this for the debugger, though, and I wonder why it would be
a problem, as the debugger does seem to clear the cache on will-navigate.
I can't reproduce this any more.  I think it was probably fixed by the devtools-core change
https://github.com/devtools-html/devtools-core/commit/0e842418fbd91a3e706135fc2c53c8233e91eeb0#diff-6e80bf9dcdd1cd5847e16016a7635ac5
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.