Bewertet mit 4,4 von 5 Sternen
4,4 von 5 Sternen
- von NetVicious, vor einem JahrBewertet mit 4 von 5 SternenThe addon works perfectly but IMHO it lacks one option. I want to delete cookies from some sites forever with one option called as example Delete+blacklist or similar. Please try to add it to the extension and it will be perfect.Hi, an option to remove all cookies from the current context will be present on the next version.
I am considering an improvement regarding the removal of cookies related to the page viewed.
However, a finer management and (in my opinion) very well done via whitelist / blacklist can be found on the uMatrix addon that I advise you.
- von mariesosa, vor einem JahrBewertet mit 5 von 5 SternenCookie Quick Manager is a very complete cookie manager with an ergonomic user interface. Unlike other addOns, it allows you to edit, backup, restore cookies, search them by domain names and so on. This addOn is perfect for who has a clue of what he/she is doing and is not only looking for a "delete all cookies" button.
The developer is also attentive to his users.
Great work, carry on!
- von Phantasma, vor 2 JahrenBewertet mit 5 von 5 SternenGreat add-on, everything works as advertised, developer is ready to help everyone - even those who never read description text. Great work, thanks for sharing.
- von Rulatir, vor 2 JahrenBewertet mit 2 von 5 SternenInitially promissing but just flat out stops working after a while. I add a cookie correctly for the domain (both dotted and not dotted, tried both ways), enter name and value, enter path '/', check the session checkbox. I expect the cookie to be sent to the domain with requests. It doesn't get sent. After a while it disappears, i.e. the search can no longer find it.
Promising but broken.
EDIT to reply to the add-on's author's response:
I know when cookies can be refreshed. The site in question is one I am developing, and the cookie is neither interacted with on the client side, nor ever set by the server; it's just a flag to enable certain debugging functionality and it used to be a GET param but we decided to switch to a cookie and use an add-on like yours to set it whenever we need.
Unfortunately I don't have time to debug your add-on, I simply need one that JustWorks™, and in fact I found one.Hi your feedback is interesting;
Nevertheless, I use this addon frequently and to my knowledge the use case you mention is functional...
However, no project is immune to a bug and you should create an issue on the project submission so that we can better understand what you are trying to do. This platform is dedicated to managing bug reports and improvement proposals while addons-mozilla.org is dedicated notations.
If you put content in the cookie that the server does not recognize as valid or that does not match the content of other cookies on the same site, or if you put information from an expired session on the server side (you can't really know that), the server may decide at any time to delete or modify your cookie.
This is totally independent of browser configuration or addon behavior.
Have you tried to visualize the status of your cookie via the Firefox development tools Ctrl+Shift+K, "Storage" tab?
You will find more information on these sites:
"This is entirely up to the user agent, i.e. the user's browser, but usually, that will indeed be when the browser is closed"
"Cookies that 'expire at end of the session' expire unpredictably from the user's perspective!"
"If there is no expiry set on the cookie, then it is a session cookie and will live as long as the browser is open, and the sessionid is valid. If the server expires the authenticated sessions periodically, then the cookie will no longer be attached to a session on the server and will therefore be essentially null."
EDIT to reply to the Rulatir's response:
Have you thought about clicking on the button "Save the current cookie" to finalize the creation of your new cookie? I only see this explanation.
I'm just asking for a full bug report describing the situation. As it stands I can only say that this addon works because I can not reproduce your approach on various sites I tested: The addon uses the Mozilla's APIs to create the cookies and the cookie is actually created in the database AND sent by GET requests with the other cookies.
- von Firefox-Benutzer 14021322, vor 2 JahrenBewertet mit 2 von 5 SternenI really want to like this add-on because the concept is great and the interface is good; however, there is a huge flaw. I will delete a cookie from a given website like Youtube using this Cookie Quick Manager but when I go into my Preferences>Privacy Security>Manage Data and open the folder, THE COOKIES ARE STILL THERE :(
I generally love Firefox but I am furious how they changed the cookies. They used to be so easy to delete but now you have to jump through a lot of excessive hoops to delete your cookies. This is a nefarious attempt to favor tracking your behavior and is total garbage. I was hoping this add-on would liberate me from the cookie fiasco created by Firefox but I don't think it works for the aforementioned reason.
- von Termie , vor 2 JahrenBewertet mit 5 von 5 Sternena worthy successor to the good old "Selective Cookie Delete". Especially the option to lock/unlock cookies is worth gold. What I would like to see is a quick option "Delete ALL cookies" (except the locked ones of course) right in the main menu, that would be really great. Saves the long-winded way via open Manager/scroll down/click trashcan-icon. Should be hopefully feasible - at least optionally, or via a keyboard shortcut? However, "thank you" for this useful add-on.
- von Firefox-Benutzer 14211488, vor 2 JahrenBewertet mit 5 von 5 SternenSo far so good. I needed an extension to edit cookie values since Firefox Quantum removed this functionality from the F12 developer toolbar, and since Google recently changed its privacy opt out mechanisms (see Personal info & privacy > Tools you can use now) to expire opt-out cookies after random short durations (30 minutes or less in some cases) and randomly 'forget' certain opt out settings. This extension did the trick. I am not happy with FF Quantum's all-or-nothing privacy permissions but that's not the fault of this developer -- I appreciate the transparency of this developer in explaining why such broad permissions are needed by the extension.
- von Firefox-Benutzer 14072894, vor 2 JahrenBewertet mit 4 von 5 SternenWhy it should have permission to modify privacy settings now?! What's required by specific features could be given by telling user what should be, and how to be edited, or at least provide an option to let extension asking users who needs these features to allow these permission.
Edit 1: Thanks for your patiently reply. Despite that the permissions are required, this extension's context support helped me in time to perfectly experience FF Context feature.
As for granting permission, there's a extension called "SiteDelta Highlight" on AMO you could refer to. Click into its settings page, which displays prompt "Advanced features (that require additional permissions) are disabled." with a button "Enable advanced features...".
Then click on that button, Firefox will prompt it requires additional permissions. So I think it should be able to grant several parts of permissions separately.
And a few advice:
1. Add context to directly "move to container" rather than only "copy to"
2. Ability to select multiple domain / multiple cookies at the same time
3. Every button in the bottom has hang-over tool-tips except the first one from left (and the forth, well it's easy to guess it is for donating). So... the first button with a trash bin icon is so disturbing I don't know what scope it applies to, neither know if it will ask me to sure before doing something.
4. Right-click context menu is not fully visible when click on item close to window border.
5. Why I couldn't copy expired cookies to other container? if it's exist when I access its website it would seem to be refreshed, so it maybe useful, why can't move it?Hi, it's a good question; the need for access rights to the API "privacy" is already explained on the presentation page of the addon:
Access and modify various privacy-related browser settings (the FirstPartyIsolation flag here).
Detecting the status of the FirstPartyIsolation option is absolutely necessary from Firefox 58 for people who want to use this extra protection.
This is a nightly feature that is currently not available other than through about:config for public versions of Firefox.
The API is here:
The way Firefox handles permissions is all or nothing: all permissions are granted or none of them are.
To my knowledge I can not ask the user to selectively accept a permission and not another.
If you have an example of this type of form, please create an issue on the GitHub so that I can explore that.
In any case if the access to the privacy API is refused, the addon will not be able to manage the cookies created with the option FirstPartyIsolation activated, even if this one is deactivated later.