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.

Thank you :)

Thank you for your encouraging review :)

Thank you for your message this is encouraging :)

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.

Basically a cookie can be refreshed/deleted by JavaScript code without reloading a page, or every time a page is viewed manually.
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:

https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#Session_cookies
--
https://stackoverflow.com/questions/4132095/when-does-a-cookie-with-expiration-time-at-end-of-session-expire

"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"
--
https://security.stackexchange.com/questions/33692/what-typically-is-the-expiration-date-of-a-session-cookie

"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.

Thanks for the review, I'm going to think about adding the option in the menu, I hope it will not be too confusing among the other deletion options.

Hi, actually the column on the right, allows you to create a new cookie if you unlock the edition by clicking on the "edit" button at the bottom.

Hi, can you develop your review so that I can see what can be improved?

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:
https://developer.mozilla.org/fr/docs/Mozilla/Add-ons/WebExtensions/API/privacy/websites

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.

Regards.