Comment 2 for bug 414759

(Far be it from me to get in the way of some snarkiness, but the browser vendors are doing exactly what they should here: implementing a CSS property with a browser-specific prefix to get implementation experience, and then using that experience to collaborate on the W3C standard definition for the property. If they didn't do that, life would be harder for Web authors, because different browsers -- or even different versions of the same browser -- would treat exactly the same property in different ways much more often.)