Completely bypassing any standards bodies, as usual, I assume. No thanks.
I'll stick to the browser made by a foundation, not a for-profit company trying to gain control over the web. I remember IE6.
I'll stick to the browser made by a foundation, not a for-profit company trying to gain control over the web. I remember IE6.
(BTW, IE gave us XmlHttpRequest. It was not introduced by a standards body. )
And btw did you miss the experiment part of all the non-standard APIs? About the only thing that wasn't was the manifest (which is JSON) and the icons.
Also, I'll give you a much worse example, that has already happened, rather than something that may happen in the future, like what you're suggesting - h.264. It "completely bypassed" the standards body as well. The standards body would've much rather used something open source and free, but since most browsers used h.264 for the video tag, and since 2 of the major browser makers, Microsoft and Apple, were unwilling to go with an open source codec, the standards body was forced to adopt h.264.
The WHATWG did not adopt h.264 as a standard, nor any other codec.