New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 795211 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit 28 days ago
Closed: Dec 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

DevTools failed to link network resource to filesystem.

Reported by sj5...@gmail.com, Dec 15 2017

Issue description

DevTools failed to link network resource to filesystem.

Platform: MacOS High Sierra Version 10.13.1 
Chrome version: Version 63.0.3239.108 

I am having issue to set up persistence with DevTools Workspaces in this Chrome version. I am aware of the new update in workspace 2.0 as in https://developers.google.com/web/updates/2017/10/devtools-release-notes#workspaces
which the DevTools suppose to do the "magic" to automatic map network resource to my local files after i drag local directory to the workspace. 

Unfortunately, it doesn't work. I expect there should be an option for me to map the resource manually as in previous Chrome version (earlier than v62) because it is really troublesome if the "magic" mapping doesn't work.

I have attached two screenshot for the resource listing in DevTools "Sources" tab. 



 
Screen Shot 2017-12-15 at 4.59.54 PM.png
175 KB View Download
Screen Shot 2017-12-15 at 4.59.23 PM.png
155 KB View Download
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
Status: WontFix (was: Assigned)
Workspaces 2.0 work only with localhost; to override files on production websites, please use "Network Overrides" feature: https://umaar.com/dev-tips/162-network-overrides/

Sign in to add a comment