This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Does Web Workbench support source maps for scss files? From what I have read, it just a matter of enabling sass debug info and enabling a few settings in chrome dev tools. In the WW settings, I checked the box to "Include Debug Info". When the css file is generated, the appropriate "@media -sass-debug-info{}" is placed above each css rule. In Chrome Canary, I have enabled the the "Enable Source Maps" checkbox as well as the "SASS Stylesheet Debugging" checkbox in the experiments section. Unfortunately, chrome dev tools does not recognize the source file from the debug info. Is there something I am missing? Here is a sample debug info from my generated css: @media -sass-debug-info{filename{font-family:file\:\/\/C\:\/Data\/eCommerce\/.com\/Development\/Nov2013\/wwwroot\/Proj.ECommerce.Web\/Proj.ECommerce.Web\/Format\/sass\/home\/_tile.scss}line{font-family:\0000348}} I am using: WW version 3.2.915.22691 Visual Studio 2012 Chrome Canary 29.0.1547.2 |
|
|
|
|
Sorry Im not entirely sure but it may be that the newer builds of Chrome are expecting an actual source map file rather than the inlined debug info e.g. The output of using --sourcemap with Sass 3.3 (e.g. http://zigotica.tumblr.com/post/51731523298/sass-compass-and-source-maps-in-webkit-devtools) WW uses Sass 3.2 as this is the current release version. We will be updating to 3.3 once this is released of course :)
|
|
|
|
