Issue metadata
Sign in to add a comment
|
Devtools fails to map CSS from workspace (regression from M48)
Reported by
m.ma...@cambiomarcia.com,
Mar 7 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36 Steps to reproduce the problem: 1. add a folder to workspace 2. try to map a css file to the file system resource 3. the file isn't recognized and chrome reload itself What is the expected behavior? Edit css on the browser editor and save it directly What went wrong? Chrome don't recognize the original file from the resource/assets folder that i added before. So i can't save my edits. I'll post a link with a video https://www.youtube.com/watch?v=ursB0wyxuaQ&feature=youtu.be Did this work before? Yes On previous Chrome release Chrome version: 49.0.2623.75 Channel: n/a OS Version: OS X 10.11.3 Flash Version: Shockwave Flash 20.0 r0 i'm in skype if need help
,
Mar 7 2016
,
Mar 7 2016
,
Mar 17 2016
It seems the problem here is that Chrome is interpreting every mapping as a folder mapping, rather than a file mapping. So if you map example.com/css/styles.css -> file://css/styles.css, Chrome interprets both files as folders instead, trying to map example.com/css/styles.css/ -> file://css/styles.css/
,
Mar 23 2016
This is fixed in Chrome Canary, and the fix will be appear in stable some time soon.
,
May 2 2016
This is still broken in Canary for me (52.0.2722.0)
,
Sep 29 2016
,
Sep 29 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by primiano@chromium.org
, Mar 7 2016Summary: Devtools fails to map CSS from workspace (regression from M49) (was: Problem using Dev Tools on Chrome 49. (On 48 works))