3 ms·
If you read the article referenced, you'd realise that web-kit isn't being picked on. The concept of using vendor-prefixes is being questioned. I'm not tarrin
by lwhi 15y ago
If you read the article referenced, you'd realise that web-kit isn't being picked on. The concept of using vendor-prefixes is being questioned.
I'm not tarring webkit with an IE brush. I'm stating that without the W3C or similar body to set standards, we would in a far worse situation.
The article spectacularly misses the point.
- tptacek 15y agoDo you have something to say about vendor prefixes? That's what we're talking about. I'm not particularly concerned about what particular blue ribbons we affix to the W3C. They're great. Now what?
- lwhi 15y agoThese links [1][2] provide some reasoning behind not using vendor extensions. The second is referenced in the article we're commenting on. I find it difficult to understand why much vitriol needs to be expended. [1] http://www.quirksmode.org/blog/archives/2010/03/css_vendor_pref.html http://www.quirksmode.org/blog/archives/2010/03/css_vendor_p... [2] http://www.glazman.org/weblog/dotclear/index.php?post/2012/02/09/CALL-FOR-ACTION:-THE-OPEN-WEB-NEEDS-YOU-NOW http://www.glazman.org/weblog/dotclear/index.php?post/2012/0...
- chc 15y agoThat QuirksMode article you posted includes an update acknowledging that it's wrong. I think the stance in the newer post it links to is more reasonable, though I'm still not sure it's all the way there.
- lwhi 15y agoThe article provides a summary of potential problems with vendor prefixes, which still stands. The author acknowledged that his suggested solution was wrong. See the redux [1] (which is actually mentioned in the article) for alternative solutions. My main concern is that the dcurt.is article misses the point entirely. [1] http://www.quirksmode.org/blog/archives/2010/03/css_vendor_pref_1.html http://www.quirksmode.org/blog/archives/2010/03/css_vendor_p...