You probably already know this, but if the CSS was generated, you could minify it and have cache-busting. It looks like this is already done for most of the site’s JavaScript. All the CSS includes have cache-busting query strings. Ditto for a good portion of images in the HTML. So currently, users get the updated CSS immediately, but their browser will display cached versions of the images included in url references in the CSS. Adding ”?blah=12345678″ to the url() references in main.css, lesswrong.css, etc would fix this. Then people wouldn’t have to worry about styling bugs due to browser caching.
You probably already know this, but if the CSS was generated, you could minify it and have cache-busting. It looks like this is already done for most of the site’s JavaScript. All the CSS includes have cache-busting query strings. Ditto for a good portion of images in the HTML. So currently, users get the updated CSS immediately, but their browser will display cached versions of the images included in url references in the CSS. Adding ”?blah=12345678″ to the url() references in main.css, lesswrong.css, etc would fix this. Then people wouldn’t have to worry about styling bugs due to browser caching.
We tried cache busting, but missed many assets. It was several embarrassing oversights.