Domain settings

[Slion]

Implement persistent domain settings including things like:

• [x] Integrate third-party app settings, see #138
• [x] Force dark mode
• [x] Delete all domains settings
• [x] Delete single domain settings - cf07dcf
• [x] Hierarchical settings - Default, topPrivateDomain and sub-domains - c76d697
• [x] Check if top private domain was deleted when coming back to domains settings
• [x] Apply default domain settings on WebView creation
• [x] Desktop mode
• [x] Javascript on/off
• [x] SSL warning Dialog - https://badssl.com/
• [ ] Image loading on/off
• [x] Ability to delete cookies from a domain
• [x] Ability to show cookies from a domain
• [ ] Enable cookies per domain
• [ ] Persist WebRTC permissions choices
• [ ] Notifications settings once we have them working #153
• [ ] Color picker #506
• [ ] Consider session specific domain settings

[ashwebcode]

I would like to suggest a domain setting to always keep cookies from a domain. So if you have cookies from this domain, it is excluded from deletion. This would be useful for staying logged into certain trusted sites

[moya2162]

This is a great feature to add. Privacy Browser has this feature and the project is open source, so maybe some of the code can be used as a starting point for this project.

[ghost]

Will this feature come in near future

[Cwpute]

I'd like to add, if Reader mode could be enabled or disabled per-domain that would be awesome.

[Slion]

There is some work going on for that feature here.

[Slion]

I'd like to add, if Reader mode could be enabled or disabled per-domain that would be awesome.

Unfortunately that would not work with the current reader mode implementation which is going to through another activity. I suggest you open a specific issue if you want to see a rework of reader mode integrated as tab in the browser activity.

[Charles7z]

Good first party cookie management is a big deal not only for privacy but ease of use.

Being able to enable only per domain is a good feature.

Another idea is auto delete all cookies, if enabled to accept cookies, except for protected domains that are set to accept cookies and possibly have a setting to "protect" that domains cookies — with kiwi browser extensions were easy to set this up, thus sites function fine because cookies are accepted but as soon as tab closed cookies for that site are cleared unless whitelisted. Good privacy + ease of use + site functional. No browsers offer this, only possibly via extensions — clearly people use it.

[The-First-King]

Domain search feature would be nice to add into the first post in case this feature might appear one day in the future.

At this moment, both Domains and Resource domains sub-menus do not have search and when a thousand entries are in the list it’s a challenge to find there what is needed.

From my opinion, without having the search, the whole idea about Domain is not usable and the easiest way is just using Default domains settings.

[Slion]

@The-First-King I agree, search feature would be nice to have, and yes once you have a lot of domains the domains lists are hard to navigate. However there is one easy way to access a specific domain settings without search and without going through the lists. While visiting a domain from the web page go to Menu > Options > Domain. Hope it helps.

[The-First-King]

This is a partial workaround because, for resource domains, it is not applicable. For example, if we would like to disable/enable JavaScript for some particular resource domains, then it would be a real challenge. Usually behind one domain there are several resource domains. The list of resource domains is approximately 3-4 times larger than for main domains.