Reminds me of the -webkit tags that became the defacto standard forcing Opera, mobile Firefox and mobile IE to support them since web developers can't be bother

Reminds me of the -webkit tags that became the defacto standard forcing Opera, mobile Firefox and mobile IE to support them since web developers can't be bothered to code to standards or update their code. If it works in Safari/Chrome it ships because of their very large user base in mobile, exactly the same situation with IE. http://css.dzone.com/articles/why-webkit-new-ie6-trap-vendor http://css.dzone.com/articles/why-webkit-new-ie6-trap-vendor http://www.techrepublic.com/blog/australian-technology/the-webkit-prefix-will-ruin-the-mobile-web/ http://www.techrepublic.com/blog/australian-technology/the-w... Not to mention Chrome developers "trying to enforce their own web standards": https://news.ycombinator.com/item?id=7184912 https://news.ycombinator.com/item?id=7184912 Progress on web standards have always been spearheaded by browser implementations before being standardized, there were many non standard extensions that Netscape implemented that IE had to add support back in the day. IE6 was a particularly bad issue because major browser releases were tied to Windows releases and Longhorn/Vista had to be reset and delayed.