If I launch a site while in Incognito, then change the shield options (e.g. block [all] cookies => block 3rd-party cookies) for that site, the setting changes for that site are not retained when I again launch that site (in or outside Incognito).
If I launch the site in regular mode, shield setting changes are retained. Not only later opening that site, but also if the site is then opened under Incognito.
under Windows 10, Version 0.65.121 Chromium: 75.0.3770.100 (Official Build) (64-bit)
Incognito mode, by definition, doesn’t keep any data/settings from your browsing session. Anything you do Incognito is wiped clean once you close the window (as far as the browser itself is concerned).
So I guess you could say, “This is a feature, not a bug.”
I don’t look at it that way. That really only applies to data exchanged with a website. If was using a password manager while in incognito (if that extension was incognito-enabled) and changed a password, the password would “stick” in the password file.
So Brave could allow site settings made in incognito to be saved to the permanent site settings without violating the spirit of “Incognito.”
In my case – I have a site setting I need to change while in incognito and have it retained – to I do that? “Exit incognito and then access the site not in incognito, then make the change” – but I don’t want to access the site while not in incognito! If there was another way to do this (a site-specific setting in a sub-menu, not in the Shields menu), a file on my disk, etc. I’d do it. ???
So it looks like Brave reads from the same Shield site-settings when it’s in regular mode or in Incognito mode. And the user can change it for the current session in either mode. But it only allows this info to be saved when in non-Incognito.
So that’s a problem if the user wants to change change the the Shield settings for a site that’s only accessed in Incognito. Ideally Brave would allow the user to change & save Shield settings in either mode. Or at least provide a way to go into a Settings menu (or, kludge, a config file) to change those settings so they’d apply.
And if you wanted to allow different saved Shield settings for normal and Incognito I’d take that too…
@WayOutWest,
We do appreciate your feedback – but I’d like to clear a few things up:
The reason Shields settings are not saved are privacy based. We want to avoid user data/actions that take place in private sessions being retained in standard browsing sessions – more specifically, the ones in which are inacted or saved automatically or not deliberately.
For example, lets say you visit a…well, lets say “adult” site, in private browsing and changing the Shields settings to view the contents of the site. If this is retained in standard sessions, we’ve essentially “leaked” this private data. So now, in both a standard or Private session, someone other than you can ascertain information about what you were doing “privately”.
However, in the case of Bookmarks, this data is saved by taking a specific action and, further, requires that this information be saved explicitly. While it’s not impossible to accidentally add a bookmark in Private browsing, it’s far less likely given the associated “save” action required. Additionally, if you’re using private browsing, you probably don’t want any of these sites saved anyway.
We can’t account for all user errors, but we tend to aim to eliminate these occurrences as much as possible. A good example of this is the decision to keep/switch to Private windows rather than Private tabs, as we had in our old iteration of Brave (Muon). Having Private tabs that appear in a standard window, while still colored differently, makes it much easier to accidentally mix up the two – switching to entirely separate windows helps eliminate this possibility.
