Bug and suggestion Rated 4 out of 5 stars
Easy to use and efficient. It doesn't try to do more than it should, so there's no bloat in the UI. Although I'm not sure how, there is probably still room for improvement!
What about controlling DOM storage on a per site basis? And also IndexDB or whatever it's called. There's a bunch of other ways than cookies to store data in our browsers nowadays, and it would be nice if they all obeyed to Cookie Monster (eventually add a checkbox for those who only want Cookie Monster to deal with normal cookies).
Since either Firefox 7.0 or Cookie Monster 1.1.0, Temporary allowed cookies are deleted when the permission is switched to forbidden (or default if default is block cookies).
This happens even with "Delete cookies when switching to forbidden" checkbox unchecked in CM's options.
For now, I would like to have Cookie Monster remain mean and lean, concentrating on managing cookies on a per-site basis.
For Temporarily Allowed Cookies, the action has always been to delete the cookies when the permission is switched to forbidden or default (if default is set to block cookies).