Yes: “change my behavior of bookmarking items instead of leaving the tabs open to read later” . . . you improvise and work around, and keep going.
There are efforts to provision certain backups; two examples:
–
I have added more tools, above - to my earlier, lengthy reply 4.
Next, a portion of a lone bird’s eye view at Brave developments, at GitHub.
–
The reason for my posting the following, is to reveal a portion of the complex territory that the relatively small numbers of Brave developers attempt to cover.
There, at GitHub, is a written flow chart system, but not technical drawings, of the Brave Browser schematics. Such that, the “Big Picture” is in the minds of the Brave developers and supporters who dare to understand and work along the workflows. But, the discoveries of some problems – that would be found by following the tracings of technical drawings – are sometimes missed.
The GitHub programmers collaboration method, relies upon decision trees that are sometimes neglected or forgotten, yet the decisions effectively set policies (“What are we going to do about that / this?” “What is the ‘expected behavior?’” “What is the expected result?'”) that vary in size and effect.
Those often little decision tree junctions appear in writing, but not on a big drawing where the effective policy would be found . . . to affect other flows.
During Brave Browser development, the old “Muon” engine was replaced by the Chromium engine. And that required some slap and dash. Sometimes a patch solved a User Interface issue, but that required a Disable Something for Now.
That “for Now” became prolonged and then left behind, until a problem – noticed by users often painfully attempting to Report a Bug at Brave Community – gets attention (if the users are fortunate to get that attention).
Somebody in development remembers something that leads to the next remembrance of a policy decision along some path of the GitHub way. And that recollection renews, for example, “What are we going to do about that / this?”
And then, an “Oops, we shut down a function at point X, when we figured that we needed to shut down a dialog window . . . and we never got back to fixing the function.” Plus a “BTW, we never settled on what the dialog wording will be.”
The GitHub way, is a supposedly organized, upstream / downstream dynamic for programming collaborators, but a some of the decisions affect other streams.
–
Brave Projects
–
Chromium Rebasing:
“Tracking tasks and work related to upgrading Chromium and maintaining / improving our integration with Chromium”
That Chromium Rebasing is one of 9 Brave Projects at the GitHub residence of Brave Software:
Sync - all Platforms, is also one of those 9 Brave Projects:
–
Brave-Browser Projects
Currently, there are 23:
The Front End
“Front End UI/UE, Url Bar/Search, New Tab page, welcome experience, branding, polish, support/docs.”
General
“Ongoing: Stability, Installation, Extensions, performance, other”
Settings
“Settings (front-end/backend)”
Shields
–
Brave Wallet Developer Information at GitHub:
“https://github.com/brave/brave-browser/wiki/Brave-Wallet-developer-information”
Brave Browser > Brave Wallet wiki – at GitHub
Brave Wallet Project - at GitHub
–
Brave Browser is, from my perspective, both in development and a prototype; and not a “Set and Forget” Internet browser - nor ready to be a Default Browser.
But even so, the competing Internet vehicles have numerous options / preferences / settings. In my view, all require study whenever performance and security are issues.
In a world of many insidious efforts working thru and around the Internet, and attempting to gather personal information, there is no chance for a comfort zone without the user learning how to manage, and developing a system for maintaining that: their management.
The more that each user learns, and troubleshoots, the more time that Brave has to focus on fixing things.
The Brave business salient to Ads / BAT / Creators / Payments / Rewards / Wallets . . . eats up a lot of the total pie chart of time available.
The battles between Fixing vs Convenience, also show in that pie chart.
The Release Notes for Brave Browser iOS, version 1.35.1, have never been revealed . . . and 1.36.x is due any day now.