I’m using Eclipse and the current solution (which I dislike) is to use “Search/Replace”. This is an error prone solution.
IntelliJ seems to support Javacsript/HTML/CSS refactoring out of the box.
From this point of view, IntelliJ IDEA seems thus to have much better support. See:
The trick is to maintain CSS clean and transparent from the beginning and clean it up as soos as things are starting to get messy.
CSS is one of those things that are terribly hard to clean up LATER.
Also, when naming selectors, choose names wisely in order to avoid coincidence with the other code of the application (at least when case-sensitive). This will help you with search & replace approach.
Hope that helps!
One possibility that I’ve come across (though haven’t used extensively yet) for css is:
The Dustme Selectors firefox addon, which is supposed to let you weed out css selectors that aren’t used when you browse a subset of pages.
Another solution that I have used for minor css checks is:
Some of the “color word to color code efficiency changes” are probably very minimal unless you have a large number of occurrences of them, but it’s useful for analysis in general as well.