Actually, I don't think so. My approach makes sure that the good promises of vendor prefixes are kept – if a feature breaks in a newer browser because of syntax changes, for instance, and the removal of the vendor prefix has simply been done through the proxy, it's crazy easy to simply fix it in the client side css, at a single line in your code. Von: Robert O'Callahan <robert@ocallahan.org<mailto:robert@ocallahan.org>> Antworten an: "robert@ocallahan.org<mailto:robert@ocallahan.org>" <robert@ocallahan.org<mailto:robert@ocallahan.org>> Datum: Thu, 9 Feb 2012 11:50:58 -0800 An: Paul Bakaus <pbakaus@zynga.com<mailto:pbakaus@zynga.com>> Cc: Simon Fraser <smfr@me.com<mailto:smfr@me.com>>, "www-style@w3.org<mailto:www-style@w3.org>" <www-style@w3.org<mailto:www-style@w3.org>>, Lea Verou <leaverou@gmail.com<mailto:leaverou@gmail.com>> Betreff: Re: Property proxies / CSS setters On Fri, Feb 10, 2012 at 8:49 AM, Paul Bakaus <pbakaus@zynga.com<mailto:pbakaus@zynga.com>> wrote: Happy with this solution, but I'm not sure everyone is. Then they won't be happy with your approach either, which achieves the same thing in a more complicated way. Rob -- "If we claim to be without sin, we deceive ourselves and the truth is not in us. If we confess our sins, he is faithful and just and will forgive us our sins and purify us from all unrighteousness. If we claim we have not sinned, we make him out to be a liar and his word is not in us." [1 John 1:8-10]
Received on Thursday, 9 February 2012 20:08:10 UTC