Microsoft, Mozilla & Opera: Don’t make -webkit- prefixes a de facto standard

Reasons for signing

See why other supporters are signing, why this petition is important to them, and share your reason for signing (this will mean a lot to the starter of the petition).

Thanks for adding your voice.

Chris H
10 years ago
The reason for signing .. hmmm....

Because I fell it is hell to develop good CSS code, which are understood by all browsers. For Example, if I use a feature from the new CSS3 specification.. The question is "Did I get all the vendor-specific codes correct, did I miss something anywhere in the code!?!"

As the different browsers use different prefixies, the code gets longer, and in the age of mobiles and smartphones.. The SIZE of the code counts a lot, especially, if you have a very long CSS document for your website(s)!

[every byte counts!]

Take a stand and sign the petition, and help make a webdevelopers life an easier to live!!!

Thanks for adding your voice.

Anthony Goodley
10 years ago
I don't wish to see a repeat of the issues IE6 caused and the ripples still continue 11 years later.

When is the web ever going to allow webmasters to write code once that works for all the browsers without hacks and stuff? This whole mess is very wasteful for everyone.

Thanks for adding your voice.

Alex Lein
10 years ago
The problem has become so bad that our webkit-specific stylesheet is now three times larger than our IE7 and IE8 css bugfix stylesheets.

Thanks for adding your voice.

Greg Jensen
10 years ago
The amount of prefix CSS needed to design a website these days is cumbersome and webkit only websites are wrong on so many levels.

Thanks for adding your voice.

Yogesh Khatri
10 years ago
To make web open

Thanks for adding your voice.

Leon Sorokin
10 years ago
this cannot be allowed to happen. the effort needs to focus on contacting major web properties and urging them to update their CSS with equivalent prefixes.

Thanks for adding your voice.

Kevin Remisoski
10 years ago
Without standards, we will create our own cross browser compatibility issues. As developers it is our responsibility to add CSS properties without prefixes to help push HTML5 and CSS3 in the right direction so validation can be updated and browser vendors can work toward compliant and universal standards.

Thanks for adding your voice.

Darius Kruythoff
10 years ago
Because the web consists of more than -webkit-*, and the goal should be to get rid of the vendor prefixes instead of making an even greater mess before the techniques even make it as a recommendation.

Thanks for adding your voice.

Virginia Rankin
10 years ago
I love the freedom and flexibility of the open web.

Thanks for adding your voice.

Kent Morrison
10 years ago
Because I am a web devolper andaweb user and seeing what might happen im worried for the future of the web. Please don't.