This CL moves the base::Feature from content_features.h to
a generated feature from runtime_enabled_features.json5.
This means that the base::Feature can be default-enabled
while the web API is co...
Brave is built on Chromium. So, by default, no they are not safe from this. Without extra effort, Brave will have this feature. I don’t know if its feasible but there’s a chance the Brave devs can remove the code from their distribution, but that’s the best case scenario and just puts them in the same position as Firefox: they get locked out because they refuse to implement the spec.
Brave devs have stated that their fork of chromium is essentially degoogled, detracked,etc. Just the browser core and built from there… They don’t automatically add in new features into their fork just because chromium does.
Is Brave safe from these shenanigans? Asking for a friend.
Brave is built on Chromium. So, by default, no they are not safe from this. Without extra effort, Brave will have this feature. I don’t know if its feasible but there’s a chance the Brave devs can remove the code from their distribution, but that’s the best case scenario and just puts them in the same position as Firefox: they get locked out because they refuse to implement the spec.
Brave devs have stated that their fork of chromium is essentially degoogled, detracked,etc. Just the browser core and built from there… They don’t automatically add in new features into their fork just because chromium does.
I see, thanks for the clarification. I wasn’t sure about the specifics of how they produce their product from the upstream source.
Brave is a re-skin of Chromium.