Add Exceptions for Clear Site Data on Close (Desktop), Startup (Android)

[Metrokoto]

Preliminary checklist

• I have read the README
• I have searched existing issues for my feature request. This is a new issue (NOT a duplicate) and is not related to another issue.
• I have searched wont fix issues and this request is not among them
• This is a feature request for the Cromite browser; not the website nor F-Droid nor anything else.

Is your feature request related to privacy?

Yes

Is there a patch available for this feature somewhere?

N/A

Describe the solution you would like

The issue here is that clearing cookies for whitelisted sites on desktop is only possible using Cookie Auto-Delete, an extension, however this leaves cookies behind (I assume it is due to the partitioning patches we have) and the only way to fully purge cookies is to use Clear Site Data manually, or On Close.
It is not even possible to do this on Android yet, as we, unlike Kiwi Browser, do not have extension support, and, the only way is to purge it manually or use Clear Site Data on Startup.

This is annoying to do, as I have various websites, as many people do, who trust not to shove tracking cookies on our browser that are used simply for login sessions.
Librewolf addressed this problem by adding a toggle to "Always Save Cookies for this Site" and making it exempt those sites from clearing cookies via privacy.sanitize-on-shutdown.

I think it it would be beneficial to have a system introduced; that, like Librewolf, allows the exclusion of sites from having their cookies removed upon clearing site data, as this may also put us more on par with them in terms of privacy / feature offerings and may even attract some Librewolf users to switch to Cromite long-term.

Describe alternatives you have considered

Android: Not possible
Desktop: Cookie Auto-Delete Extension

[uazo]

however this leaves cookies behind (I assume it is due to the partitioning patches we have)

ah, that's not good. but I am in doubt about the effectiveness of that extension.

addressed this problem by adding a toggle to "Always Save Cookies for this Site"

yes, I think I will try that too, but only when I am sure that the message communication will be switched off between different browsing contexts (see uazo/bromite-buildtools#322).

Imagine a situation like this:

1) TOP FRAME SITE A.COM 
2)        |--- IFRAME SITE B.COM

3) TOP FRAME SITE C.COM
4)        |--- IFRAME SITE B.COM

5) TOP FRAME SITE B.COM

if 5) is able to communicate with 2) and 4) deletion of storage is the only possibility

[g-k-m]

however this leaves cookies behind (I assume it is due to the partitioning patches we have)

ah, that's not good. but I am in doubt about the effectiveness of that extension.

addressed this problem by adding a toggle to "Always Save Cookies for this Site"

yes, I think I will try that too, but only when I am sure that the message communication will be switched off between different browsing contexts (see uazo/bromite-buildtools#322).

Imagine a situation like this:

1) TOP FRAME SITE A.COM 
2)        |--- IFRAME SITE B.COM

3) TOP FRAME SITE C.COM
4)        |--- IFRAME SITE B.COM

5) TOP FRAME SITE B.COM

if 5) is able to communicate with 2) and 4) deletion of storage is the only possibility

Wouldn't that be solved by just blocking third party cookies?

[uazo]

Wouldn't that be solved by just blocking third party cookies?

no, these are different things.