By James Edwards

Dust-Me Selectors: Now Compatible With Firefox 3!

By James Edwards

Today we released Dust-Me Selectors Version 2.1, the handy Firefox extension that trawls through your style sheets and cleans up unused selectors.

The primary change with this version was to add support for Firefox 3. Making this change wasn’t a difficult task for me — all I had to was upgrade to Version 1.0 (beta 3) of base2, and add a couple of UI tweaks.

Firefox 3 support aside, you should notice no huge difference in the performance or feature set.

For more information, to read documentation and to install the new version, check out Dust-Me Selectors on

Incidentally, if you’re interested in getting the most out of Firefox 3, you might like to check out our free eBook, Firefox 3 Revealed, available for download now.

  • Great, I have been waiting for this. :)

  • nice, use this extension quite a bit

  • sounds good for a bit of css optimization

  • Could this not be hosted on so that we get notified of updates?

  • Jas

    Firefox could not install the file at

    because: Not a valid install package

  • MarvinLeRouge

    Thanks A LOT (i starved for this update :D )

  • Anonymous

    Any plans for checking embedded stylesheets as well as external stylesheets?

    P.S. Hello James and Ben.

  • killerog13

    Hmmm, it says that it isn’t compatible with Firefox 3.0.1.

  • Sorry, my bad! Please grab the 2.11 update and you should be fine.

  • WebSupport

    Is there a limit to the size of the site map that this plugin can spider? (or the size of the resulting datafile). I have a large site, the complete sitemap is about 20meg. I had to divide it into four parts to get it to run (and it takes about a day to parse each file). It seems to stop towards the end and won’t go any further…

  • axing

    v2.11 doesn’t support with portable firefox 3.0.5.

    I installed v2.11 on my clean portable firefox 3.0.5, but it keep crashing while starting up firefox. :(

    Any solution?

  • sandiegoscott

    Dust Me (v2.11) doesn’t work for a site located on a local drive, so can’t be easily used for development. Why is that?

  • What aspect of it doesn’t work? I’m aware that the spider can’t read sitemap files from the local filesystem, but apart from that it should all be fine?

    On a side note – have you considered using a local server for development? You’ll find it a lot more productive.

Get the latest in Front-end, once a week, for free.