7 comments

[ 4.8 ms ] story [ 32.6 ms ] thread
For a bit of a different flavor, here's the one I've been using that accomplishes the same aims:

http://gist.github.com/649724

It's a good bit more compact, recursively refreshes the CSS in all frames in the window, and uses a timestamp instead of a long random number.

I've been using this one for many many years. Is your version better / more efficient in any way?

http://david.dojotoolkit.org/recss.html

Nah, don't think so. I wasn't aware of any existing so I just wrote one. Apologies for lack of novel idea :P
Both are new to me. Your link compares against a string, and his looks for the type in the DOM? Not sure which is better.

Could a better mind please explain which is more appropriate?

Forgive me for asking, but what's wrong with just reloading?
Maybe you are six levels deep into a JS-heavy webapp? If you reload, you would have to re-navigate to what you want to fix.