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...
That’s not even the biggest level of “we told you this would happen.”
They pulled this shit previously with other standards (WebHID). Where they proposed a terrible standard, and then implemented it ignoring all feedback. Only last time it played out over months, and this time… weeks?
There’s a “we told you this would happen” going on here.
If chromium didn’t have a monopoly amongst browsers, they would have a much harder time pushing this through.
Imagine everyone using a browser built by an advertising company.
That’s not even the biggest level of “we told you this would happen.”
They pulled this shit previously with other standards (WebHID). Where they proposed a terrible standard, and then implemented it ignoring all feedback. Only last time it played out over months, and this time… weeks?
Sweet jesus.