Rated 1 out of 5 stars

this review is for 0.2.4 version of addon.
It's not working with FF3.6.17
in Firebug console i see:"CSS Usage: initializing extensions"
and when i click "Scan" button i see:"CSS Usage Warning: storage not yet available".

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

Not Working in FF 3.6.16 Rated 1 out of 5 stars

Nothing doing on the latest 3.6.x build. Any chance for a fix? Or will I have to switch to ff 4 (and lose several other addons) to get this one working?

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

Not working at all (OS X - FF 3.6.16) Rated 4 out of 5 stars

Hi,
It's a quite nice and useful add-ons I've used sometimes with FF 3.6.14. But now after update FF to 3.6.16 this add-ons stops working : ( ... Actually I don't know if the problem is about 3.6.16 or what else. I just guess it. In short nothing happens pressing the "scan" button.
I could try to update FF to 4.0 and see if this fix it. But unfortunately for the moment FF 4.0 has troubles with some other add-ons I use.

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

Rated 4 out of 5 stars

Seems to be a cool plugin. I had a problem with using the version 0.2.3 of this plugin in combination with Firefox 3.6.x on Windows. It reported a warning about the storage in the Firebug console and the CSS Usage tab did not display any data.
The issue got resolved when I upgraded my Firefox to version 4.
Just thought I share this here in case anyone else encounters a similar problem.

Thanks, Markus - www.cross.tv/markus

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

"export cleaned css" in HTML section does nothing Rated 4 out of 5 stars

very nice add-on, but I was disappointed by the fact that the "export cleaned css" link in the HTML section does not appear to work. I was hoping it would detect old-school embedded presentation attributes and convert them to CSS.

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

Rated 3 out of 5 stars

@dcuffman Use the Dust-Me Selectors addon. Set up a page with links to every page of your site (site map if you don't already have one) and have Dust-Me scan every page that's linked to.

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

Rated 4 out of 5 stars

Great addon but....

Isn't a bit dangerous? What I mean is, it shows in red text what the browser isn't picking up BUT unless you scan the entire website, there's no way of knowing 100% for sure if its ok to remove a given attribute or class, right?

My problem is, I'm working on a very complex and large Drupal 7 site, which for me to click through every page and ajax condition is simply not reasonable or a viable option.

This is a wonderful addon, don't get me wrong. :) Thank you for your efforts! It just seems one has to really know his css classes before using this tool or risk the possibility of removing css that is used on another page or for a given condition that is not current met.

Or am I missing something?

Thanks!

C.

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

Love it. Want more =) Rated 5 out of 5 stars

Loved it, it really is a great addition to Firefox's long list of to have addons.

Just a suggestion, since firebug shows what are the css declarations that are not in use on a given element, could it be possible to have a report that would tell me that the line-height on the class .xkcd is never used?

Thanks for contributing with your time and with this awesome plugin.

This review is for a previous version of the add-on (0.2.1). 

Rated 4 out of 5 stars

Great and much needed app. A few things that would make it even more useful:

- content folding or some other means to filter results to a specific css file
- better logic for hovers etc. If is never user, you can be sure that :hover is never used either.
- distinguish rules that are used but not effective (overwritten by another rule with higher specificity) from rules that are actually used

This review is for a previous version of the add-on (0.2.1). 

Rated 5 out of 5 stars

I would first like to thank you for a great firebug add-on and second I have a feature request. I think if you could add the ability to minimize the css groups it would be helpful.
As an example say you've scanned 3 pages and end up with stats for 3 html pages along with various css listed by files and some belonging to an inline group. If we could minimize these various groups to just their header line it would make things a bit more manageable when dealing with large amounts of css. Additionally, it would be nice if we could re-maximize each scanned pages css after scanning multiple pages instead of just having a readout of what had been scanned on the previous pages.

Anyway thanks again for all the work thus far.

This review is for a previous version of the add-on (0.2.1). 

Rated 4 out of 5 stars

This is a great addon to Firebug. Teun - great job and thank you! @daelmo is right about the commenting of unused css. If the "export cleaned css" option would comment the entire block, this addon would instantly become part of my optimization workflow.

This review is for a previous version of the add-on (0.2.1). 

A little request Rated 4 out of 5 stars

Great Add-on. Congratulations and thanks. It's just one thing that bother me: the cleaned css generated has a bunch of semantic errors coz of the comments of the css selectors. Would be nice if the string formatter of the add-on would be smart enough to generate a error-less css file. A classic error: /* .theClass */ {...} or /* .theClass*/, otherClass {...}

Thanks

This review is for a previous version of the add-on (0.2.1). 

In support of previous feature request Rated 5 out of 5 stars

I think that this https://addons.mozilla.org/en-US/firefox/reviews/display/10704#review-165462 feature request makes sense, do you know probably of any other tool which can do that?
Btw. since the addon is called "CSS Usage" I sort of even expected it to do what @xybermatthew describes, i.e. being able to extract CSS Usage inside the particular part of the page

This review is for a previous version of the add-on (0.2.1). 

In support of previous feature request Rated 5 out of 5 stars

I think that this https://addons.mozilla.org/en-US/firefox/reviews/display/10704#review-165462 feature request makes sense, do you know probably of any other tool which can do that?
Btw. since the addon is called "CSS Usage" I sort of even expected it to do what @xybermatthew describes, i.e. being able to extract CSS Usage inside the particular part of the page

This review is for a previous version of the add-on (0.2.1). 

Rated 3 out of 5 stars

Great add-on. I only have one request. It would be great if one could isolate the CSS to a selected region within the page. For example I would like to see just the CSS rules of a nested div and all of it's containing elements (unlink firebug which only shows the CSS rules for the selected element only), including all the inherited rules and without any of the rules used for other regions of the page. In other words, I want to get all of the styles for a form or a table, etc. within a page but no other rules used on the page such as those used for the surrounding paragraphs, lists, etc.

This review is for a previous version of the add-on (0.1.7). 

Unlikely

Seems to me like that would be more appropriate for Firebug than for "CSS Usage".

Rated 5 out of 5 stars

this is and works great !

one request: it would be GREAT if this could - in addition to the site's css - scan css applied by stylish. If that's too hard to implement you could also simply provide the option to manually select a css file for a page that you then have your extension scan for coverage. This would be very useful for designing userstyles for pages. (like the page gets updated and thus many rules are obsolete etc)

This review is for a previous version of the add-on (0.1.3). 

Rated 4 out of 5 stars

I agree with rakisisesindekibalik.
Very good add-on but auto-scanning when panel is enabled would be a must.
Works nice with FF 3.5

This review is for a previous version of the add-on (0.0.5). 

Added Autoscan

AutoScan is now added in version 0.0.9

Rated 3 out of 5 stars

Tried with 3.1 beta3 and seemed ok.
I would like to see
1- Ability to see or export "cleaned" css code as in html validator.
2- An option for auto scanning so I wouldn't need to hit scan at every page.

This review is for a previous version of the add-on (0.0.5). 

export: no, autoscan: yes

1. This might be a bad idea since it is very likely you'll throw away some CSS that is only used in extreme situations (for error messages or whatever)
2. Agreed it would be nice, it's on the todo list.

not suit for current final release of FF (3.0)?! Rated 2 out of 5 stars

I like to see it available for current full version of Firefox!

This review is for a previous version of the add-on (0.0.5). 

True, only Fx 3.1 and higher

Because of new features introduced in Fx 3.1, CSS Usage only works with 3.1 and higher. I hope Forefox 3.1 will be released shortly so this is no longer an issue.

Rated 2 out of 5 stars

ok

This review is for a previous version of the add-on (0.0.5).