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

Issue 807282 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 796251
Owner: ----
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

Auto-mapping simply doesn't work at all

Reported by oli.henn...@gmail.com, Jan 30 2018

Issue description

DevTools 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.
 
Labels: Needs-Triage-M64
Cc: lushnikov@chromium.org vamshi.k...@techmahindra.com
Labels: Triaged-ET OS-Windows
@lushnikov: Could you please confirm whether this issue is similar to that of 796368, 794965 and 796251.

Thanks!

Comment 3 by l...@chromium.org, Jan 31 2018

Mergedinto: 796251
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment