title: Sass/SCSS support in Chromer Developer Tools
body: <p>Previously, until the very recent time (up to Chrome 27, as far as I can tell), Chrome Development Tools, with help from Chrome Experiments, supported Sass (SCSS to be precise) "inspection".</p>
  
  <p>The support manifested in ability to inspect the site's CSS file and if the CSS was compiled from SCSS using <code>--debug-info</code> (SCSS 3.2.7), then in CSS panel:</p>
  
  <p><img src="https://i.stack.imgur.com/9SQoW.png" alt="enter image description here"></p>
  
  <p>instead of CSS file link - you'd see the corresponding SCSS file link and you could click it and it would open the file in resources in the exact SCSS rule that contributed to the CSS rule being inspected (much like you can with CSS file).</p>
  
  <p><strong>For whatever reason, this has stopped working with (my) latest Chrome update.</strong></p>
  
  <p>This is important to the work I am doing at the moment (SCSS reorganization of a large project) so I am asking: did anyone experience the same (I have it on all machines I have access to) and, more importantly, <strong>does anyone know how to fix it (without hunting down older Chrome versions)</strong>?</p>
  
  <p><em>I wasn't sure what would be the proper SE channel, but since it relates to development - here it is</em></p>
  
  <blockquote>
    <p>P.S. The paths SCSS generates seem to be correct, since in FireSASS they are shown and accessed correctly</p>
  </blockquote>
  
  <p>The same happens on any channel I tried - Release, Beta, Canary</p>
  
  <p><strong>Update 18.06.13</strong></p>
  
  <p>Since it seems that the old (<code>--debug-info</code>) days are gone, I will accept @electric_g answer as the only possibility.</p>
  
  <p><img src="https://i.stack.imgur.com/6KCel.png" alt="Sass support in experiments"></p>