Issue metadata
Sign in to add a comment
|
Unable to map network resource in Developer tools
Reported by
peter.al...@gmail.com,
Dec 19 2017
|
||||||||||||||||||||||||
Issue descriptionDevTools failed to link network resource to filesystem. Platform: Mac Chrome version: 63.0.3239.108 What are the details of your project? Locally served files on localhost 8081 App server Wildfly Src files in file system Assets failed to link (or incorrectly linked): 1. All css and js assets 2. Not tried any others. I can map the drive successfully, and it shows the source files. When I open one of the files either from Network or Filesystem it suggests mapping the file. If I hit 'more' it will bring up the dialog box and offers 'Establish the mapping now...' When you press 'Establish etc' it correctly finds the file to map at the top of the list. When you select the file from the list it just goes back to the 'Establish the mapping now...' dialog. No mapping has taken place. If you close the dialog and edit one of the files then the other one is not changed. This was working successfully up until last week, and then stopped working after it got confused on a breakpoint. I have deleted Chrome (including settings) according to the instructions here https://support.google.com/chrome/answer/95319?co=GENIE.Platform%3DDesktop&hl=en and reinstalled.
,
Dec 21 2017
This issue seems to be similar to that of https://bugs.chromium.org/p/chromium/issues/detail?id=794946, CC'ing lushnikov@chromium.org for further inputs. Thanks!
,
Dec 22 2017
Duping into similar issue #794946 , feel free to undupe or revert if both are not same. Thanks!
,
Dec 23 2017
Un-duping this from that overly-general issue
,
Dec 8
Workspaces 2.0 is imperfect and there's no feasible way to make it work for everybody. Archiving since we currently don't have resources to allocate towards improving Workspaces story. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Dec 19 2017