Issue with source map
Reported by
mhmd...@gmail.com,
Aug 31 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2837.0 Safari/537.36 Steps to reproduce the problem: 1. add a local workspace 2. connect to network mapping 3. modify sass in element tab. 4. click on the sass file link to navigate to sources tab 5. want to look into local modification. What is the expected behavior? Modification made in the sass has to be reflected on the sass and not the css What went wrong? Issue 1: no view local modification option seen when the source files are network mapped. Issue 2 : able to see the modification If I open the history tab directly but the modification made on elements tab are show in the history of the css file not the sass. P.S:changes made to the sass file on the sources tab is rightly reflected on the sass file. Did this work before? N/A Chrome version: 54.0.2837.0 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 22.0 r0 issue similar in canary and dev version.
,
Aug 31 2016
,
Sep 1 2016
,
Sep 1 2016
,
Sep 2 2016
,
Dec 5 2017
There's no way to edit SASS file from elements panel (there used to be a LiveSASS experiment that allowed that, but it was discontinued). When editing styles from elements panel, all modifications are done for the CSS file, thus the history of local modifications exist only for the CSS file. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mhmd...@gmail.com
, Aug 31 2016