I moved to a new browser (from firefox to waterfox) and it didn't sync my cookies, using this tool I was able to transfer my cookies so I didn't need to re-login to every site and such!

Awesome! Just what i was looking for.

Works fine in conjunction with the Forget Button extension.

What I don't understand is why this extension, ostensibly, "requires" containers (as noted in the Options > General...Tabs section of the Firefox browser. I hate "containers" but it seems to work just fine without that weird and confusing "feature" that I prefer having nothing to do with.

Perfect. Parfait

Amazing add-on!

When I first installed this add-on, I was initially impressed with the user interface but once I actually began attempting to use it's features it rapidly became clear that the developer(s) have made absolutely no attempt at helping the learning curve. This isn't helped by the fact that the UI needs a lot of polishing to smooth out quirks. The quirks are not only annoying, but they also don't help when trying to figure out how the add-on works.


User Interface needs polishing:
Things that seem minor can actually be major annoyances for the user. For example...

The Subdomains checkbox, when clicked, will reset the user's current selected index in listbox. Why wouldn't it first store the text associated with the selected index, then after it populates the listbox, loop over the items until it finds the index of the stored text? Or maybe there's a better way of holding the user's position in that list, I don't know. It may seem trivial, but it's not. That checkbox should function more like a toggle, so the domain that the user is working on will persist between toggle-on and toggle-off.

The Refresh button has the same effect on the listbox. Whatever cookie I had selected before clicking refresh..... I have to find it again because the list has been reset to index0.

There's a setting labeled 'httpOnly' but then it's mouseover tooltip explains that it's really talking about Https. Why make it confusing? Am I setting it HTTPS-only or not?

The IsSecure and IsSession checkboxes are confusing in functionality and description. IsSecure's tooltip says virutally the same thing as the httpOnly checkbox's tooltip.

The IsSession checkbox says that it forces the cookie to expire at the end of session. You're assuming the user knows what you mean by "session." Do you mean browser session? The cookie gets deleted when I close my browser? Do you mean the cookie gets deleted if I log-out of this website? These things are obvious to YOU, but not a new user, especially one who's not a web designer.

Context: this container selection dropdown doesn't explain what it is, most FireFox users dont have the toolbar visible. I wasn't even aware that Mozilla added this goofy idea until I looked into why this add-on needs 'Container Permissions'. (I was thinking, what the heck is a container?) These are a concept I will NEVER use. LOL!

There's definite bugs in how the IsSecure checkbox works. Sometimes I check it and click save, and then suddenly BOTH IsSecure and Is IsSession checkboxes are active. Other times I click IsSecure and save and the IsSecure box becomes unchecked. Other times I click httpOnly and then save, and then httpOnly becomes unchecked and then IsSecure+IsSesson both become checked. WOW!

The above is related to this next problem. When I click the Save button twice, it seems to be acting like a Toggle. The httpOnly, IsSecure, IsSession boxes will check and then uncheck. And they keep toggling on and off if I keep clicking Save. What the heck could be the purpose of that? If that's intentional, then you need to explain what it's doing. However it makes no sense to me. Is the save button doubling as a Load-saved-data function or something?

I honestly dont' have time to spend, trying to figure out what is a bug and what is the intended design, all at the same time as trying to learn how to make the add-on work for my needs. Apparently it's not as 'Quick' as advertised. Maybe I'll come back and give it another try after it's had more time to smooth out the UI. But by then, I may have found the cookie add-on that works the way I need.

Netscape export missing header which should be "# HTTP Cookie File" or "# Netscape HTTP Cookie File", which is the reason for the 4/5 stars, not a huge deal as it can be added manually but there's no reason for it not to be part of the export.

Essential

If you spend lot of time developing webapplications or doing online testing this application helps a lot with dealing with all the issues that can arise with cookies and stored localstorage easily. It is much bettar than going through the browser "Clear Recent History" that deletes all the data not selectively. Thumbs up for this extension

Очень удобный Cookie Manager.

The developer of this addon should be ashamed to continue to claim features that have repeatedly been shown to not work and Mozilla should be ashamed for recommending broken garbage.

I am not sure how Mozilla can recommend this.
This extension is broken in so many ways.
There are many thread about failure and inability to delete cookies.
There are also threads showing it is broken when it comes to edit of cookies (can't even change a session cookie to expire on a specific date.
This addon is only good if you want to view your cookies.
This addon is WORTHLESS as a Cookie Manager.
This addon does not allow managing MOST cookies and instead treats them as read only.
This addon is a failure compared to the addons it claimed to be inspired by.
Further the support has been non-existent.

What criteria does Mozilla use when recommending addons that they would recommend this BROKEN and INCOMPLETE excuse for a cookie manager. According to the "Recommended" status Mozilla has reviewed it for functionality. Every person at Mozilla who has installed or even looked at this addon and said it deserves a Recommended status should be barred from any code or review positions for gross negligence and incompetence.