EightShapes/Blocks — Issue #38: Versioning assets - cache buster
Author: francisrupert
Created: 2012-03-01 22:26:57+00:00
State: open
Labels: Bug

**Ask:** version any non-author-controlled, Blocks-specific referenced JS and CSS by way of query string, e.g. `file.css?v0.0.1`

**Why:**

1. Guarantees some browsers won't hold onto cached asset. They treat `file.ext?bleh` as new asset to load.
2. Versioning is a good thing, no?

Chrome drove me batty not letting go of cached assets - specifically blocks.css and blocks.js (and I *think* core.js). Solved it by *temporarily* adding a query string to the asset *core.js*

e.g. `$('head').prepend('');`

However, it doesn't stick after removing. And yes, the old "clearing cache" thing did it - but I typically treat that as absolute last debugging step.