Helpful, but not completely. Rated 3 out of 5 stars
This will get me in the neighborhood of what I want...
The xml sitemap business doesn't work, so if that's what you want, you should wait for the next version. That's what I need, the aggregate.
The selector bit is nice, but it would be cool to see if actual rules go un-applied, like in cases where an element can adopt rules from multiple selectors. Dust-Me selectors never claims to be able to do this, so I can't really fault it. But it does mean that if you really need this tool, you probably need more information if you want to really clean up your CSS,
If your site is more than one page or has DOM changes, it's going to take more work to be confident that a selector is really unused.
It's good information, what little there is, and the View Saved Data interface is thoughtful. I look forward to the next version.
Thanks for the review.
Sitemap indexes are not yet supported, but ordinary sitemap XML files should be fine. Can you tell me what the problem was, or give me a URL of the sitemap you tried to parse?
Where an element adopts rules from multiple selectors, all of the selectors will be checked, including those which only apply through inheritance. But you're right when you say that this alone is not enough to be completely sure that a selector is unused -- you have to take it as the starting point to reduce manual checking. I welcome any thoughts you have on how this could be improved.