Оценено на 4,6 из 5
Оценено на 4,6 из 5
- от kolAflash, месяц назадОценено на 4 из 5Great extension!
Just a few questions:
Is there any hope that Mozilla will support this for the new Firefox>=80 on Android?
Why not activly asking users if cookies should be deleted after leaving a site?
Or alternatively making AutoDelete the default and activly asking users if cookies should be kept.
Also has anyone compared this extension with:
I've been using "Forget Me Not" for about a year and I'm currently trying to evaluate which one may be more suitable for my parents and other less technical experienced people I know.
- от Rick, месяц назадОценено на 5 из 5Why can't this extension honor my settings?
My setup is Block All Cookies, Enable First Party isolation, use some Containers for some sites that i use a lot and Set Cookies for Some Sites that need cookies but that i don't use that often to Allow for Session.
i DID-(before i disabled it) have cookie auto delete set to not enable container support, and it wouldn't touch the Containers, which was perfect, And i was hoping cookie auto delete would delete the cookies that i set "Allow for Session" so Firefox wouldn't have to be Restarted for them to get deleted. BUT i noticed every site was getting cookies deleted, then i saw "You must enable cookies in the browser as this extension will replace the internal cookie manager."
Well first, i didn't Enable cookies, and Cookie Auto Delete didn't honor MY Settings and Enabled cookies automatically, which isn't the right thing to do. "You must enable cookies in the browser", well i never Enabled cookies in the browser, but cookie auto delete did.
The wording should read "Cookie Auto Delete WILL enable cookies in the browser automatically as this extension will replace the internal cookie manager.
Second, Can and Will cookie auto delete ever honor my settings and let me Block All Cookies and just delete the cookies that i have set to Allow for Session?
To me that would make cookie auto delete Perfect in my opinion. And i could probably give it only a 4 star rating for these 2 shortcomings, but i won't as one issue is a Wording issue and maybe cookie auto delete should ask before Enabling cookies, but i don't think it's that big of a deal since it needs cookies to delete. Fixing the wording pretty much solves that issue and asking to enable cookies before doing it would go the extra mile.
And the second issue, maybe can't be done, i don't know, But i would think that Blocking All Cookies, Honoring that Setting and just Deleting the cookies that are set to Allow for Session is possible.
i hope this is possible and will be added to cookie auto delete. i would appreciate these being addressed and looking forward to a reply from the CAD Team.
Thanks in advance and all you do for us browser users.
Before i submitted this review, i just thought that i haven't tested this Block All Cookies and cookie auto delete Deleting just the Allow for Session cookies in my Ungoogled Chromium and Brave Browsers.
i probably won't test this for a few days. if you know that would be great.
Thanks again and sorry for the long review but i was trying to be explain and be as thorough as possible.
Ответ разработчикаопубликовано месяц назад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.