Problem using Dev Tools on Chrome 49

[Michele Marri]

I've a new problem when chrome automatically updated to 49. 

Seems that dev tools are updated on the new version,
but now i can't use anymore the "map to file system resource" tool that i use everyday.

Re-installed 48 and all seems to work.

In short:

i work directly in the browser, using the inspector and editing css in the right panel (dev tools).

I've mapped the site folder with the workspace and now that's showing in the resource panel.

The bug shows up when i try to map the css file to the workspace, it seems to not recognize the original from the folder.

Chrome reload the old itself.

I'll post a video to show.

I'm using last OSX 10.11.3 and latest Chrome 49.0.2623.75 (64-bit)

thanks in advance

https://www.youtube.com/watch?v=ursB0wyxuaQ&feature=youtu.be

[Primiano Tucci]

Hello Michele,

can you please file a bug about this in crbug.com, component: Platform>DevTools>JavaScript ?

This is the kind of issue that should be tracked there and will go lost and forgotten otherwise.

If you can provide repro steps would be great. Make sure you attach the youtube link there.

Thanks reaching out.

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

[Michele Marri]

Done

[Luke Rissacher]

I'm also having this problem. Is there a way I can downgrade to Chrome 48 and disable automatic updates until this is fixed?

Thanks,

-Luke

[Gosku]

Same problem here, with Chrome 49  in Centos 7,

[dhw]

Thanks for the report!  You can add a STAR to the following issue to be notified of updates to bug fixing:

https://bugs.chromium.org/p/chromium/issues/detail?id=595347  -  Chrome v.49 disappeared links to local source files