In Google's defense, and basically because I like this particular feature, I have to point out the obvious ... most new browser features happen before and not a

In Google's defense, and basically because I like this particular feature, I have to point out the obvious ... most new browser features happen before and not after standardization. The standardization process is meant for reaching agreement among browser makers and to provide clear specs for those features. But it isn't meant for exploration. That has always been the case. Even Mozilla does it. And if not, then you can't really get the browser vendors to agree on mostly anything a priori, without market validation. Standardization works as a refinement of already existing work. E.g. Google came with NaCL/PNaCL which was basically their own ActiveX, Mozilla came with Asm.js in response and the end result was Web Assembly, which is objectively better than both and that wouldn't have happened without that prior art. The W3C doesn't guard what gets implemented in browsers. It never did. And if browser makers willingly participate in the standardization process, we should thank them, because they can always stop doing it. Because really, retreating from the W3C would mean absolutely nothing for computer illiterate people.