It’s time for action. We, as users, must demand developers, vendors, and companies to stop implementing the WebKit only prefixes on CSS properties. Let’s make this the Open Web or good, and not repeat the mistakes of the past. Your voice matters.
It sounds like something from a galaxy far, far away, but in truth it was not that long ago that the web was littered with sites that proudly proclaimed “works best in Internet Explorer.” Thankfully those days are over. IE6 no longer dominates the web.
But, while IE6 may be a thing of the past, the root problem — websites that work in one and only one web browser — sadly, remains.
Web developers have created a WebKit-only web. Instead of writing code that will work in any browser, which might mean adding an extra three lines of code to their CSS rules, some of even the largest sites on the web are coding exclusively for WebKit.
The problem is bad enough that on Monday at the CSS Working Group meeting, Microsoft, Mozilla and Opera announced that each are planning to add support for some -webkit prefixed CSS properties. In other words, because web developers are using only the -webkit prefix, other browsers must either add support for -webkit or risk being seen as less capable browsers even when they aren’t.