We cannot simply have read-only access to certain browser settings like global cookie behaviours, unless we request for the privacy API, which allows read AND write of certain settings. We only recently implemented a workaround for the detection of firstPartyIsolation that removes the privacy API permission request.

In any case if you disable the cookies then you probably wouldn't need this extension in the first place. We don't enable anything on our own (with the exception of containers as by default any extension that requests the 'contextualidentities' API automatically forces Firefox to enable it (this is a browser 'feature') and this permission cannot be made optional yet).

That being said, however, if you did enable any of the 'other browsing data' cleanup options, then we would create our OWN internal cookie for it. This goes through the Cookie API so I suppose that bypasses whatever you have set (maybe it is a Firefox 'feature')? The reason, as mentioned many times as well as in documentation, is that only cookies can be enumerated for domains, while the other browsing site data types either require that we already know the domain to clean beforehand, or a specific timeframe to remove the data from (e.g. An hour ago, a day ago, all) which is not what this extension does so that is out of the question.

We cannot access the browser internal cookie manager (the one for block/allow for session) as there is no API for it (at least on Firefox) so you'll still need to manually configure the expression through our extension, otherwise the default behaviour of removing cookie(s) if no other tabs with that domain is open will apply. With our own internal cookie being cleaned it then triggers the cleanup for the other browsing types.

This is better off as a support issue as it allows for better commenting and discussion without having to edit the original post much.

Please open a support issue through our GitHub repo for discussion.
https://github.com/Cookie-AutoDelete/Cookie-AutoDelete/issues/new/choose