@Saoiray ,
It is long:
There have been a number of posts and replies, where members of the Brave Community have been wondering about (among Brave Browsers), the descriptions and distinctions between:
- a Private Window
- the –incognito command line flag and / or “incognito mode”
- the Private Browsing Only switch effects
- what some call “Private Mode”
- what some call “Private Browsing”
I use Brave Browser:
- because it has shown to not be a memory hog – in contrast to Firefox (that has a long-standing memory leak problem?)
- for Privacy and Security
There are also, many posts and replies at this Brave Community (and over at the Brave residence, at GitHub) re the ongoing struggle between:
Brave Browser, as far as i have read, is mostly designed for, intended for, privacy and security. That means, taking steps to be, and remain, secure.
And the steps to be so secure, have always included dumping caches, cookies, history, other data, in addition to logging out of websites.
And the steps include, being certain to have systems for backing up important data (egs. passwords and bookmarks) to external drives / media so that, such data is not depending upon, for example, a particular Internet browser – for recovery.
From my perspective (the context preceding) I tend to be willing to troubleshoot, from a state of preparedness. I want to find out, what causes a problem, and not have to worry about losing any data.
So, I wondered what the action of pressing on the " + " icon . . . causes re the creation of a new tab and/or new window:
- when “Private Browsing Only” switch is ON
- when “Private Browsing Only” switch is OFF
- when the immediately previous tab or window was NOT Private
- when the immediately previous tab or window was Private
- when Brave Browser was [somehow] started with the “–incognito” flag
- when using Brave Browser after the computing device has been thru a period of idle, including Sleep (sometimes, Brave Browser will then “just suddenly crash”)
In other words, I was considering the various switches and their combinations of settings.
And, I am considering the inexplicable (to the lay person) re behaviors, events, and happenings of Brave Browser . . . that are sometimes the result of, developers putting a halt to some process / sub-routine of Chromium, in order to apply a bandaid over, or remove entirely, some pop-up window’s dialog “that might confuse users.”
Because, developers are busy and asked to cover vast territories, instead of remaining focused on an un-disturbed programming stream of conciousness.
That conundrum (sp?), is why, it seems to me, that the Brave Ads / BAT / Creators / Payments / Rewards / Wallets . . . problem has remained as a major reason for a lot of bug reporting to Brave Community and to the Brave residence at GitHub. (Yet, Brian Bondy has thankfully been ever-present, here at the Brave Community, trying to corrale the problems.)
And the developers’ territorial conundrum is also why, the Sync problem has been long-lasting. (Yet, there are recent indications, now, that various little bugs that lingered for a long time, in the “backlog” stacks, have gotten a lot of attention.)