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

Issue 794946 link

Starred by 17 users

Issue metadata

Status: WontFix
Owner:
Last visit 28 days ago
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

DevTools failed to link network resource to filesystem.

Reported by asafm...@gmail.com, Dec 14 2017

Issue description

DevTools failed to link network resource to filesystem.

Platform: Win
Chrome version: Version 63.0.3239.84 (Official Build) (64-bit)

Hi, auto mapping not working for me at all.

I added my projects folder to workspaces, but auto mapping doesn't happen.
What can I try?

Can I disable workspaces 2.0?

Thanks,
Asaf

 
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
 Issue 795551  has been merged into this issue.
Cc: lushnikov@chromium.org sc00335...@techmahindra.com
 Issue 795515  has been merged into this issue.
Status: WontFix (was: Assigned)
1. Note: workspaces now work only for localhost:// domains. To work with real websites, please use "network overrides" feature: https://umaar.com/dev-tips/162-network-overrides/

2. No, workspaces 2.0 cannot be disabled

Cc: vamshi.k...@techmahindra.com
 Issue 796136  has been merged into this issue.
 Issue 796251  has been merged into this issue.
 Issue 796886  has been merged into this issue.
 Issue 797041  has been merged into this issue.

Comment 9 Deleted

I enabled 'DevTools Experiments', but don't see "Override requests with workspace project" (file attached). Cannot edit sources in external editor (only in DevTools panel). Files have same names and content, but cannot get 'green ball'.

Issue with mappings is still actual

Chrome version:  Version 63.0.3239.132 (Official Build) (64-bit)
2018-01-08_132458.png
15.1 KB View Download
OS Windows 2012
Hi Asaf, do your .map files contain 'sourcesContent' ?

That fixed it for me:
https://bugs.chromium.org/p/chromium/issues/detail?id=805308#c3
I'm curious why a regression that's remained unfixed after two releases would be given priority 3? 

It looks like in addition to the six bugs that have already been merged into this one there have been many more about how automatic mapping fails since this bug was filed, all which add up to a combined 150 stars. That doesn't count the similar bugs which were already closed with status of wontfix.

809731 - 16 stars
794233 - 7 stars
793241 - 63 stars
794233 - 7 stars
794443 - 2 stars
794965 - 2 stars
795211 - 2 stars
795515 - 3 stars
796136 - 1 star
796251 - 8 stars
796809 - 1 star
799571 - 4 stars
801223 - 4 stars
802251 - 4 stars
805308 - 1 star
806142 - 2 stars
809727 - 3 stars
810627 - 2 stars
812681 - 2 stars

My request is that these get merged down into canonical bugs and prioritized appropriately as regressions.

Sign in to add a comment