Re:The Mobile Web should just work for everyone
by talmand on Monday August 04, 2014 @04:41PM
(#8133897)
Many of these properties no longer require the prefix for most browsers. For these properties having the webkit prefix only, without the non-prefix property to cascade to, is a problem. I recall many demos, examples, and live sites not displaying as expected in Firefox because the developer decided to use only the webkit prefix. If the webkit team were to start removing the webkit prefixed properties then those sites would have even more broken views.
Re:The Mobile Web should just work for everyone
by bzbarsky on Tuesday August 05, 2014 @12:00AM
(#8135439)
They're initially prefixed because the standard is not finished.
Many of them are _still_ prefixed because WebKit has a policy of never removing prefixed features, even if they implement the unprefixed one. So people feel no compunction about using the prefixed stuff in production, and since they only test in WebKit they don't notice when they're using the -webkit-prefixed version even though every single browser (or every browser except WebKit, in some cases) supports the unprefixed standard version.
On the one side I want to make a ramble about why it takes so long for those standards to finish and unprefixed CSS3 and beyond is possible, but on the other hand - without actual real-life use, how can you find all the edge-cases and practical application to create a complete standard?