Added css folder to workspace, devtools always uses network version and not filesystem version
Reported by
ra...@7oaksgroup.com,
Jan 11 2018
|
|||
Issue descriptionDevTools failed to link network resource to filesystem. I dragged my css folder into workspaces, it shows up in DevTools under Sources -> Filesystem. The folder there is greyed out, I'm not sure if that is significant. Then if I go to Elements -> Styles and try to directly change an element's css it shows the name of the css file but if I hover over the name it is always pointing to the network version of the file instead of the filesystem version. Platform: Mac - High Sierra Chrome version: 63.0.3239.132 What are the details of your project? - Source code (if any): not public - Build System: none - HTTP server: node HTTP/nginx/apache... Assets failed to link (or incorrectly linked): 1. all files in all folders - specifically see screenshots for css files If possible, please attach a screenshot of network sources navigator which should show which resources failed to map
,
Jan 11 2018
,
Dec 8
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 |
|||
Comment 1 by ra...@7oaksgroup.com
, Jan 11 2018