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

Issue 799571 link

Starred by 5 users
Status: Archived
Owner:
█ lushnikov@chromium.org
Last visit 28 days ago
Closed: Dec 8
Cc:
█ lushnikov@chromium.org
█ vamshi.k...@techmahindra.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

Mapping to resourses not working

Reported by fasterwo...@gmail.com, Jan 5 2018 
DevTools failed to link network resource to filesystem.

Platform: WIN
Chrome version: Versión 63.0.3239.84 (Build oficial) (64 bits)

What are the details of your project?
- http://jaguariu.com/crmbiosidus_dev/main.php#INICIO
- Build System: 
- HTTP server: APACHE

Assets failed to link (or incorrectly linked):
1.html
2.css
3.js

If possible, please attach a screenshot of network sources navigator which should
show which resources failed to map
err.PNG
48.3 KB View Download

Comment 1 by fasterwo...@gmail.com, Jan 5 2018 

I add folders to workspace and then I try to map the web to the resourses as I used to do before, so I could edit CSS files and save them. But it doesn't work anymore.

Comment 2 by vamshi.k...@techmahindra.com, Jan 10 2018

Cc: lushnikov@chromium.org vamshi.k...@techmahindra.com
Labels: Needs-Triage-M63 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 rocki...@gmail.com, Jan 10 2018 

Please fix mappings for js/css, that are broken till "Workspaces 2.0"
Or please return "previous worspaces", if possible. 

We cannot edit mapped files in external editors

Win 2012
Chrome Version 63.0.3239.132 (Official Build) (64-bit)

Comment 4 by came...@remitly.com, Jan 11 2018 

More details -- https://bugs.chromium.org/p/chromium/issues/detail?id=801223. This also doesn't work for me. The 2.0 version of workspaces (https://developers.google.com/web/updates/2017/10/devtools-release-notes#workspaces) just totally broke a previously working project.

Comment 5 by eostroukhov@chromium.org, Jan 11 2018

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

Comment 6 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