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.
It may be dead to its users anyway depending on how forceful Google is with this. If Brave doesn’t work on 98.8% of all websites with advertising or indeed on 49.5% of all websites (approximately Google’s ad network’s reach), it becomes as niche as lynx.
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.
It may be dead to its users anyway depending on how forceful Google is with this. If Brave doesn’t work on 98.8% of all websites with advertising or indeed on 49.5% of all websites (approximately Google’s ad network’s reach), it becomes as niche as lynx.
Yeah Brave would probably be fucked then. If you can’t have privacy anyway, might as well use Chrome.