zlacker

> then began to implement their websites with alpha versions of their proposed web standards that only their browser properly implemented

That is the standardization process. The W3C won't ratify a standard that does not have draft implementations in the wild.

>>moron4+(OP)
No. The standardization process does not call for you to make your public facing, extremely visited website use Polymer/ShadowDOMv0. You can implement your API and make a demo website/offer a beta test on your website so that people can try it out.

Making it the default and making the fallback only reasonably accessible by installing an extension that will rewrite your links (that all send back to the alpha-using version), causing every browser that isn't Chrome to slow down to a crawl while you happily display a "Hey, did you know the web is faster with Chrome?" isn't working through the standardization process, it is weaponizing it to sabotage other browsers.