New issue
Advanced search Search tips

Issue 756579 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Mapping, editing and saving a file in workspace has no effect

Reported by gregrei...@gmail.com, Aug 17 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
1. Created folder ~/Downloads/workspace/
2. Go to https://nodejs.org/en/
3. Open devtools > sources, right click nodejs.org and add folder to workspace, selecting above folder, click "allow"
4. Create file dnt_helper.js under workspace with console.log('hello');
5. Find network file of same name and map to filesystem resource, choosing dnt_helper.js
6. Reload page, nothing printed to console.

What is the expected behavior?
Load dnt_helper.js off of disk instead of network, and print "hello" to console.

What went wrong?
Nothing printed to console.

Did this work before? N/A 

Chrome version: 62.0.3188.0  Channel: canary
OS Version: OS X 10.11.6
Flash Version: 

See screencast.
 
workspace.mp4
3.7 MB View Download
Screen Shot 2017-08-17 at 2.08.41 PM.png
46.7 KB View Download

Comment 1 by l...@chromium.org, Aug 17 2017

Status: WontFix (was: Unconfirmed)
Thanks for the report.  It seems to me that the intent is to have a remotely served file (https://nodejs.org/en/static/js/dnt_helper.js) be ignored, and have Chrome instead load your local file (~/Downloads/Workspace/dnt_helper.js) and execute instead.

Unfortunately, the Workspaces/persistence feature isn't designed for this.  It's intended for an 'opposite' use case common with locally served webpages: changing a file (https://localhost:8080/en/static/js/dnt_helper.js) in DevTools sources panel/styles pane will affect a locally stored file (~/Downloads/Workspace/dnt_helper.js).

Fortunately, I think your use case is addressed by this other work-in-progress feature to patch network requests.  https://bugs.chromium.org/p/chromium/issues/detail?id=754371

Please let me know if I'm misunderstanding your use case or if you have further questions.  If you have specific requests on the 'request patching' feature, please comment on the other crbug.
Looks like I completely misunderstood the intent of the workspace feature. Thanks for the response and sorry about the noise.

Sign in to add a comment