title: Chrome workspaces with fingerprinted assets
body: <p><a href="https://developers.google.com/chrome-developer-tools/docs/settings#workspace">Chrome workspaces</a>: let's say I map local CSS files to those served by my local http server. Everything works great and I can modify the files in-browser and upon page refresh my changes persist.</p>
  
  <p>We happen to fingerprint our assets so that they are referenced via urls like <code>styles.css?longuniquehash</code>. Great practice - this way we can use aggressive caching and be sure the most recent assets will be used by the client.</p>
  
  <p>However, this backfires a little with workspaces as the mappings get lost whenever the url is updated. In a nutshell: we map <code>styles.css?123</code> to the local resource, we change it and on page refresh it comes back as <code>styles.css?234</code> which has to be mapped again.</p>
  
  <p>We're using <a href="http://getcassette.net/">cassette</a>, but the problem can be reproduced on any setup with fingerprinting. Is there a setting or a workaround I'm missing?</p>