Interesting stuff. There may well be a way to keep the browser from caching such auxilliary files, but I don't know it off the top of my head. Perhaps a META no-cache in the head of the main document would do it, but I haven't investigated that.

It's also interesting that your temp css files were overwritten when the page was reloaded. Different browsers and different configs may exhibit different behaviour, of course. If the cached css files are never referenced, it seems like an awful waste of space. :-)

I love getting into the temp directory and poking through some of the css and js files...they can be very instructive.

I stumbled across a css trick all by my lonesome a few days ago, though. The boss wanted a text link to still respond to rollover by exhibiting a hover state even after being visited. Of course the typical default at that point is to not display a hover state.

In the past, the only pseudo-classes I've used for links were the "normal" ones: link, hover, active and visited. But (and it seems obvious in hindsight), you can roll your own: visited:hover will display a hover state after the link's been visited. Imagine my glee. Maybe you other webgeeks out there knew that, but it was a pleasant surprise to me. :-)