Yes please bring it back.

Assigning the issue to lushnikov@ as per the issue id: 796251. 
lushnikov@ - Please have a look into the issue.

Thanks...!!

It looks like Chrome looses syncing after the first detected change. 

Have a look here as well: https://stackoverflow.com/questions/48462761/chrome-devtools-workspace-2-0-loses-syncing-with-css-files-after-reload

Same problem here.

https://stackoverflow.com/questions/48462761/chrome-devtools-workspace-2-0-loses-syncing-with-css-files-after-reload Doesn't seem to be the same issue. No matter what I do, adding a folder to a workspace does not result in any linking between resources. "site.com/themes/{themename}/css/resource.css" is the file, adding a folder "themes/{themename}/" or "{themename}" to the workspace fails to link the local "themes/{themename}/css/resource.css" to the network resource... Some documentation on what the "magic" method used to assign pairs would be very welcome, that way we at least have some idea what we should be doing...

I seem to be having similar issues running macOS Sierra.

While working on this, could you look at supporting webpack builds? In the instructions at https://medium.com/@rafaelideleon/webpack-your-chrome-devtools-workspaces-cb9cca8d50da there are specific mapping instructions, but now we can't use them and I can't get it to work without these instructions.

Actually, it looks like my code is being mapped properly - it looks like my issue is https://bugs.chromium.org/p/chromium/issues/detail?id=807996 - I was expecting my scss files to update.

In looking at https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component:Platform%3EDevTools%3EAuthoring it seems like there are probably more than a dozen duplicates of this (e.g., https://bugs.chromium.org/p/chromium/issues/detail?id=794564)- can they be closed to centralize attention?

Agreed the new inferred mapping was not ready for production. Even when mapping works it can take 10 seconds to refresh a page after modifying a file. 

There is a thread @https://stackoverflow.com/questions/48032249/chromes-map-to-file-system-resource-not-working-after-update. I've tried all the workarounds and none of them work. You do realize this is a big deal for a developer with an established workflow. Please give us an ETA for when to expect a resolution.

As of version 71.0.3559.6, this issue still persists. There is no reliable way to map local resources. The feature is basically entirely broken. The previous manual mapping system, while slightly more effort to set up, was actually useful and worked quite well. Considering how long this report has been open, it seems prudent to revert to the old behaviour while the issues with the new system are worked out.

Same problems here.

 Issue 809727  has been merged into this issue.

 Issue 799904  has been merged into this issue.

 Issue 816596  has been merged into this issue.

 Issue 807996  has been merged into this issue.