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...
You can spoof that, so they know it’s not a good enforcement mechanism as it can still be sidestepped by extensions. I had to do that for a corporate client when their intranet tried enforcing Chrome on Windows only.
If Google et al. tried enforcing user agents, they would just lose even more tracking information, as everyone would be scrambling their user agents. This cannot be so easily sidestepped.
No, it is a problem for all browsers, present and future, period.
The point is that major websites, even government ones might decide to be only available on Chrome.
So much for internet freedom…
They can already make that decision by looking at your
User-Agent, but this gives them an incentive to block other browsers. That is terrifying.You can spoof that, so they know it’s not a good enforcement mechanism as it can still be sidestepped by extensions. I had to do that for a corporate client when their intranet tried enforcing Chrome on Windows only.
If Google et al. tried enforcing user agents, they would just lose even more tracking information, as everyone would be scrambling their user agents. This cannot be so easily sidestepped.