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.
No brave users don‘t care. Brave proved how untrustworthy they are and in any case their business model is unethical yet they still have a cult like following plus a group of crypto bros that are obsessed with getting digital pennies.
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.
I have to imagine they will strip it because if they don’t, it’ll be dead to all of their users.
No brave users don‘t care. Brave proved how untrustworthy they are and in any case their business model is unethical yet they still have a cult like following plus a group of crypto bros that are obsessed with getting digital pennies.