Support editing sources in the Debugger and trigger source overrides
Categories
(DevTools :: Debugger, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: ivan.wills2, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
163.60 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/111.0
Steps to reproduce:
In the dev tools' debugger tab it would be good if we could override individual source files, save them and reload pages with those saved over written files.
This would greatly help with testing in production on compressed source files with no map files.
This is a feature that Chrome has had for many years (and the main reason I have to go back to Chrome from time to time)
Actual results:
View a file in the debugger and try to edit it nothing happens.
Expected results:
View a file in the debugger, edit the file and "save for overrides".
When you reload the page, the saved over written code is run not the original source code.
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'DevTools::Debugger' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•2 years ago
|
||
Hi Ivan,
Thanks for filing.
Interestingly we just landed this feature "file overrides" in nightly recently. It just allows you override individual files (as you mentioned). Maybe you can try it out, and see what you think, and give us feedback on how we can improve it.
Thanks so much.
See attached image
Reporter | ||
Comment 3•2 years ago
|
||
That is good to see but it's not exactly as easy to use as the chrome version as you can't edit it in the browser as you need to use an external editor. Also I seemed to have to shift reload the page before the overwritten file was visible.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 4•3 months ago
|
||
(In reply to ivan.wills2 from comment #3)
That is good to see but it's not exactly as easy to use as the chrome version as you can't edit it in the browser as you need to use an external editor. Also I seemed to have to shift reload the page before the overwritten file was visible.
See bug 1933455. Chrome seems to automatically disable cache when setting up the override, which explains the difference here.
Description
•