Dust-Me Selectors is a standalone extension that finds unused CSS selectors, and is particularly useful for updating legacy sites, allowing you to throw away all those redundant rules without worrying that something, somewhere might be using them.
CodeBurner for Firebug, as its name suggests, is an extension to the popular developer tool, Firebug, and extends it with searchable reference material for HTML and CSS.
We’ve been beavering away behind the scenes on updates to both these extensions, waiting for the final version of Firefox 3.5 — and now that it’s been released, here they are!
But that’s not nearly all! Both new versions also bring a host of improvements and new features:
New features in Dust-Me Selectors Version 2.2:
- new tabbed preferences dialog that’s neater and more user-friendly
- added a new spidering preference "don’t spider external sites", which resricts the spider to pages on the same domain as the sitemap
- bugfixes to make "find…" and "spider…" keyboard triggers more reliable cross-platform
- improved error handling throughout
- removed two unecessary preferences to streamline the spidering logic: "ignore www difference" and "ignore fragment identifiers" in URLs, both of which are now enabled all the time
New features in CodeBurner for Firebug 1.2:
- improved search algorithm gives better results
- special search now includes "other attributes that are valid for this element" as well as those which are actually defined for it
- code examples for CSS properties now include direct links to live examples online
- the original search term is now indicated in search results
- slightly modified license clarifies the distinction between "use" and "redistribution"
Both of these updates have been uploaded to the Mozilla Add-ons site, however since all submissions are reviewed manually, it may be a day or so before they become available from there, or through the automatic updates channel. So if you can’t wait that long, you can grab them straight away from SitePoint:
As always, we welcome your comments and feedback on both of these extensions — and if you’ve any ideas for features you’d like to see, please don’t hesitate to let us know!