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

Issue 794965 link

Starred by 2 users
Status: Duplicate
Merged: issue 670330
Owner:
█ lushnikov@chromium.org
Last visit 28 days ago
Closed: Dec 2017
Cc:
█ lushnikov@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Mapping to filesystem not working after update to 63 version chrome

Reported by pvvnxdem...@gmail.com, Dec 14 2017 
DevTools failed to link network resource to filesystem.

Platform: ubuntu 17.10
Chrome version: 63

What are the details of your project?
- Source code (if any): https://github.com/dementor5/510833-device
- Build System: none
- HTTP server: none, local files

css files failed to link, button "map to network resource" not showed in context menu.
chrome 63 mapping error.png
164 KB View Download

Comment 1 by chenwilliam@chromium.org, Dec 14 2017

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

Comment 2 by krajshree@chromium.org, Dec 20 2017

Cc: lushnikov@chromium.org
 Issue 796368  has been merged into this issue.

Comment 3 by lushnikov@chromium.org, Dec 20 2017

Mergedinto: 670330
Status: Duplicate (was: Assigned)
- On the screenshot, the css files are mapped (thus the green dot).
- The "map to network resource" button is removed in favor of automapping

Note: filesystem urls don't work nice with workspaces in general, thus duping to the FS workspaces bug.
►

Sign in to add a comment