Chromium extends Google’s control over the web platform. Google engineers write specs for new APIs. They get rejected by Mozilla and Apple on privacy and secur

Chromium extends Google’s control over the web platform. Google engineers write specs for new APIs. They get rejected by Mozilla and Apple on privacy and security grounds. Google implements them anyway. Other Chromium-based browsers get these APIs as a result. Then they start popping up on sites showing Safari and Firefox “failing” to implement them. Then web developers ask why Safari and Firefox are so “behind” in implementing “web standards”. This mechanism is how the web standards process is being subsumed into “whatever Google wants” instead of being a collaborative effort between multiple rendering engines. Google should not be able to unilaterally decide what is and isn’t a web standard.