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...
The biggest problem is if Google can influence all the major websites (banks, e-commerce, news sites, streaming services, social media, etc) to adopt this standard.
Would it be possible to create a fork of chromium to avoid google’s influence?
The biggest problem is if Google can influence all the major websites (banks, e-commerce, news sites, streaming services, social media, etc) to adopt this standard.
They’ve done it before with AMP.
And fuck AMP, it’s a fucking travesty.