Issue metadata
Sign in to add a comment
|
Auto-mapping simply doesn't work at all
Reported by
oli.henn...@gmail.com,
Jan 30 2018
|
||||||||||||||||||||||||
Issue descriptionDevTools failed to link network resource to filesystem. Platform: Win 10 Chrome version: Version 64.0.3282.119 (Offizieller Build) (64-Bit) There is nothing special on the project - it's just a private enterprise project, so no public link to the project available. I used the Chrome's workspaces and mapping-http-resource-to-workspace-file feature now for years - but this new 'magic' i-can-reveal-the-mapping-to-the-workspace feature seems to be a total crap - It simply does not work. Nothing happens, nothing mapped, we can't develop any more with Chrome like we did for years. As we can't even map manually, the workspace feature is now totally useless.
,
Jan 31 2018
@lushnikov: Could you please confirm whether this issue is similar to that of 796368, 794965 and 796251. Thanks!
,
Jan 31 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Jan 30 2018