On Brave iOS, site-specific Shields overrides set in normal tabs are ignored in Private Tabs. This makes Private Tabs inconsistent with normal tabs and forces me to reconfigure Shields every time, which in context of iOS terminating Brave every day or 6-12 hours, it translates to reconfiguring shields every day.
Example:
• Global setting = JavaScript blocked
• In a normal tab, I allow JavaScript for google.com
• In a Private Tab, google.com still shows JavaScript blocked (global setting), override is not applied
@ml35 you’re describing how things should work. Private browsing is designed to be temporary and isolated. Any changes you make during that session should not carry over to future sessions. If it did retain your site-specific settings, that would mean it was saving data about you from private sessions, which would completely defeat the purpose of privacy, wouldn’t it?
no, it would not at all. the “data” saved is not something that the site would know about… unlike screen resolution or cookies or anything actually shared as cached information between the site and the browser.
imagine having uMatrix desktop addon (sort of an equivalent to the brave ios shields) not remember the per site setting while opening an incognito window! that would be absurd, yet somehow this absurdity made it’s way into a mobile browser.
@ml35 I think there’s a misunderstanding here. A private window doesn’t actually hide anything from the websites you visit; it simply prevents your browsing history, cookies, and other site data from being stored on your device after you close the session.
If site-specific settings were saved from a private session, that would indicate some trace of your visit remained, which goes against the purpose of private browsing.
When you open a private window, it starts fresh with only your global settings applied, without any saved site data or preferences. That behavior is intentional and aligns with the basic concept of privacy in browsing.