Rated 5 out of 5 stars

Simply genious. I tried it, I loved it.
Works automatically and dedects all Selectors on your Webpage, that you have active. GREAT. THANKS

Problem if CSS minified Rated 3 out of 5 stars

I was excited to come across this add-on to make the job of CSS clean-up much easier. However, after scanning my site and selecting the option to clean the main CSS file, it says it is “too minified.” The css in this file was created by us using the WordPress theme framework Headway and their CSS live editor. I checked with them, and indeed the CSS we input into the live editor is automatically minified before being added to the main stylesheet. They said there is no way to unminify it.

Is there anyway to still use the add-on? All the CSS is unminified when inserted in the live editor.

Note: I did try switching themes and copying over the CSS, but it didn’t seem to work correctly, which is probably due to the fact that so much of our html coding is done within the Headway theme framework and does not carry over to other themes…

Brothercake - thanks for your reply.
I don't know how the unminifier function would solve the problem. If I copy my minified CSS into the unminifier and then copy the unminifed version back into the CSS file, my theme just automatically minifies it again....
Any other solutions appreciated! I haven't come across another tool quite like yours...

Okay, so WordPress must be automatically minifying the live editor CSS and then saving it in only that format, disposing of the original.

The CSS cleaner can't work without line-breaks, because that's how the CSS is parsed. In order to handle that, I'd have to rewrite the CSS parser.

That's not entirely out of the question though -- if it's going to be a problem for a lot of people. Or maybe add an unminifier function.

There are tools online that do that (eg. http://mrcoles.com/blog/css-unminify/) so that might help you in the meantime, and I'll give some thought to whether that functionality could be added to the extension.

RESPONSE: yeah you'd have to copy the unminified CSS into a different stylesheet that isn't parsed by WP. But then I guess that's not possible, if WP automatically minifies every stylesheet that appears on the page. There's no other solution I can think of, sorry. I'll investigate whether the extension can support this, but there's no other workaround I can suggest in the meantime.

WOW! Thank you kind brothercake!!! Rated 5 out of 5 stars

I processed a mockup I've been working on based from a template (I only wanted certain elements) using Dust-Me. The CSS file went from 93KB to 6KB without having to manually go through all these usused properties. This plugin just saved me a full day's work cleaning up the file.

Appreciated greatly.

Good Add on Rated 4 out of 5 stars

I like it. Finding it very useful for integrating a plugin into my existing site where dozens of css selectors are competing with each other and breaking my design. There is one bug I found, though, so I couldn't give it 5 stars. Read on because I found a work around for it until it gets fixed. Hopefully it will help someone else.

I also had the problem of the data view popup not appearing, like what Nouvelle Vape mentioned. It showed up as expected the first time I ran it, but after tweaking my css and running the add-on again, the data view failed to appear in the new popup window.

I'm running Windows 7, and I saw the popup window's presence was accounted for as an additional icon alongside the firefox icon in the taskbar, but when I hovered over it for the window preview, it showed my webpage in firefox and an empty screen as my two windows to choose from. When I clicked on the empty window preview, I got nothing. It just went to my desktop.

I don't know what's causing it. Its almost as if the popup data view window is "stuck" as a minimized window. I did discover that if I hovered over the "empty" window preview, right-clicked on it, and chose "maximize," the window would appear properly, granted at full screen, but I could see the data.

I will also email this bug report to the address provided on the add-on page.

Okay that's useful info, thanks. I will investigate this further.

Great tool but I have a problem... Rated 4 out of 5 stars

Hi there,
I discover this amazing tool and start using it, but since a few days I have the following problem:
At the end of a Spider Sitemap process the window Dust-me Data does not pop up, impossible to see the selectors and start the "clean" process. The Dust-me data appears on the ms windows Tab bar but impossible to display the window.
Any idea?

If you go "View stored data..." from the toolbar-button menu or the main tools menu, then what actually happens?

Rated 3 out of 5 stars

Honestly, it's a great concept and exactly what I was looking for, but I am not sure it is working correctly.

On a tryout the add-on said certain stylesheet had 408 unused selectors (and around 200 selectors used), when according to inspect it has 396 selectors, total.

I don't know if it has something to do with my version of FF (31) or if its just outdated or broken. Not sure I can trust the information.

So you're saying there's a difference between the web inspector (or Firebug?) and what dust-me produces?

There's a number of possibilities, the least likely of which is a fault in dust-me. In fact it's more likely that dust-me is correct and the inspector is wrong; or at least, different -- dust-me understands a number of selectors that Firefox doesn't support, and which therefore won't show up in its inspection.

Or it might be to do with dynamic content that was present when scanned but not when inspected. Or it might be to do with a difference in how the different tools represent the CSS DOM.

I can't really say more without knowing what URL you tested it on. If you'd like to drop a line to the support email, I'd be happy to investigate.

Works perfectly, good features, zero learning curve. Rated 5 out of 5 stars

This is not only cool and useful but lean and tight, unmistakable UI. A good example of good software! Works flawlessly on my machine. Not only finds my unused selectors from my sitemap, it offers to create a copy with the unused either commented or deleted. Version info from FF about page:
Mozilla Firefox for Linux Mint
mint - 1.0

Great, Not Perfect Rated 4 out of 5 stars

This works very well in functionality. It's helped me find clean up CSS (though having to go to every page on a site does take a bit). My only problem with it is that there is no high-res icon. When I have it placed in the new dropdown menu, it looks blurry. Add the high-res icon, and I'll change this to 5-star.

EDIT: I mean the dropdown menu that shipped with Firefox starting with Australis. I'm using a 6 year old Dell, with a screen that is not in any way retina.

You mean for retina screens? I'm gonna do that soon -- just got a 2013 macbook myself, so it really does stand out :-)

EDIT: In which case, I don't know what you mean. Can you upload a screenshot?

Works really well. Rated 5 out of 5 stars

Excellent app, does exactly what it says. Great for cleaning cruft out of huge messy css files. Very impressed with the "spider" function.

Doesn't work Rated 1 out of 5 stars

Does nothing when I click on "view data".
I have latest updates of Firefox and Dust me installed.
Complete waste of time.

Can you give me some more information to isolate what this problem might be -- the precise Firefox version number, which platform you're running it on, and whether there are any errors in the console.

Причем тут json и csv? Rated 5 out of 5 stars

С одной стороны плагин то, что нужно. Казалось бы, можно найти на сайте неиспользуемые стили, скопировать лишь используемые, и заменить ими стили. Но нет, почему-то сделано так, что сохранить используемые и неиспользуемые стили можно лишь в json и csv. Почему нельзя сделать сохранение в css формате - непонятно.
Нужно возиться с конвертация json формата в css. Хотелось бы, конечно, иметь сразу возможность сохранения в css.

Попробуйте "чистые" кнопки в диалоговом окне "Просмотр сохраненных данных", которые производят версию таблицы стилей, в которых неиспользованные селекторы удаляются.

(Try the "clean" buttons in the "View stored data" dialog, which produce a version of the stylesheet in which unused selectors are removed.)

Rated 1 out of 5 stars

Definitely not reliable - I have selectors listed as unused that are actually used on various pages

This user has a previous review of this add-on.

If you know that a selector is unused, then you can right-click and select "mark as used".

But generally, the places where Dust-Me will fail to find selector use, is where those selectors are only used by content which is generated by JS after page load or by user interaction (e.g. a lightbox which only appears when the user clicks something). It's not possible for the spider to detect that kind of thing, so you have to scan such pages individually, using the Automation preferences and mutation events, to detect dynamic changes in content.

Unable to parse selectors data (JSON syntax error) Rated 4 out of 5 stars

Dust-Me Selectors works well for me but inthe web site I'm working on doesn't work.He say me No StylesheetsandUnable to parse selectors data (JSON syntax error) Can you help me please?
This is the url

What's the web site URL?

Rated 5 out of 5 stars

very good, easy use.

errors Rated 4 out of 5 stars

α) Με την εγκατάσταση όλα οκ. Στη χρήση τώρα...κάμποσα selectors τα διαγράφει ενώ χρειάζονται...πρέπει να τρέξεις όλα τα js της φόρμας-σελίδας, η αφήνει πράγματα που δεν χρειάζονται.πχ έβαλα το bootstrap.css το καθάρισε αρκετά αλλά με το χερι το έκανα αρκετα μικρότερο.β) Όταν το επαν-ενεργοποίησα χάθηκαν τα Data στη popup σελίδας...

Εάν χρησιμοποιείτε το "Αυτοματισμού" προτιμήσεις που μπορείτε να πάρετε την επέκταση να ανιχνεύσει αυτόματα, ενώ μπορείτε να περιηγηθείτε και να αλληλεπιδράσετε με τις σελίδες. Κάντε κλικ στα στοιχεία, αιωρείται πάνω από τα πράγματα - ό, τι αλληλεπιδράσεις είστε scripting για - και αυτό θα σας βοηθήσει να βρείτε επιλογείς που χρησιμοποιούνται μόνο με JavaScript.

(If you use the "Automation" preferences you can get the extension to scan automatically, while you browse and interact with pages. Click on elements, hover over things -- whatever interactions you're scripting for -- and this will help it to find selectors that are only used by JavaScript.)

Ilya Rated 4 out of 5 stars

Cant find the option to save cleaned up css file. After scanning online webpage can't use the option "view stored data". (FireFox 24)

The cleaning controls are in the view data dialog, but I don't know of any reason why you wouldn't be able to access that. What happens when you try?

Ain't working in FF22 Rated 3 out of 5 stars

All the functions are greyed out, can't access preferences or scan any page. Maybe it needs updated for FF22+ ?

This review is for a previous version of the add-on (3.01.1-signed.1-signed). 

Doesn't work Mac 10.7.5 FF 23.0 Rated 1 out of 5 stars

Non of the functions work, can't even get dialog box, preferences can't save, etc

This review is for a previous version of the add-on (3.01.1-signed.1-signed). 

Rated 1 out of 5 stars

Doesn't work on firefox 22

This review is for a previous version of the add-on (3.01.1-signed.1-signed). 

Yes, that notes above do say that. Changes in F22 have broken the extension, and I'll release a fix as soon as I get the chance.

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.

This review is for a previous version of the add-on (3.01.1-signed.1-signed). 

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.