title: Chrome/Sass Sourcemaps, changes made in inspector not saved in SCSS file
body: <p>Here's a quick summary of what I'm talking about:</p>
  
  <p><a href="https://medium.com/what-i-learned-building/b4daab987fb0">https://medium.com/what-i-learned-building/b4daab987fb0</a></p>
  
  <p>When using Chrome with workspaces and sourcemaps set up, and the local/network files linked, I can use the Chrome web inspector (under the Elements -> styles pane) to recognise the location of the selector in the correct SCSS file. In addition, I can click that, be taken to the SCSS file, make a change and then save it successfully to the file system. However, what I have previously had working is changes made in the <strong>elements->styles</strong> panel to get updated in the SCSS file (i.e. If I make a change in the elements tab and check the SCSS file within chrome it should have changed it).</p>
  
  <p>Instead it makes the changes to the CSS file. Obviously this is not very useful as:</p>
  
  <ul>
  <li>It will be overwritten as soon as the SCSS file is changed</li>
  <li>It means Chrome will show styles which are not in the SCSS file, even after reload, as they <em>are</em> saved persistently in the CSS file</li>
  </ul>
  
  <p>I've tried this on both OSX and Windows, using Sass 3.3.6.
  Can also confirm that it's not the "../" issue referred to in #9
  <a href="https://code.google.com/p/chromium/issues/detail?id=273384">https://code.google.com/p/chromium/issues/detail?id=273384</a> as the sass file is now within the css file. There are also no style.css?ver=x extensions on the stylesheet tag.</p>