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

Issue 817266 link

Starred by 1 user
Status: Archived
Owner:
█ lushnikov@chromium.org
Last visit 28 days ago
Closed: Dec 8
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

workspace mapping not working

Reported by thorsten...@gmail.com, Feb 28 2018 
DevTools failed to link network resource to filesystem.

Platform: Win
Chrome version: 64 (x64)

What are the details of your project?
- Source code (if any): created with angular/cli
- Build System: angular/cli "ng build"
- HTTP server: angular/cli "ng serve"

Assets failed to link (or incorrectly linked):
1. all assets and do not stop on any debug stopmarks
2.
3.

If possible, please attach a screenshot of network sources navigator which should
show which resources failed to map
network.PNG
13.0 KB View Download
file system.PNG
16.0 KB View Download

Comment 1 by susan.boorgula@chromium.org, Feb 28 2018

Labels: Needs-Triage-M64

Comment 2 by alph@chromium.org, Mar 3 2018

Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 3 by lushnikov@chromium.org, Dec 8

Status: Archived (was: Assigned)
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