> So contrary to your comments, they're doing this because the W3 said that it's time to do so. My point is that support for prefixed CSS properties should not

> So contrary to your comments, they're doing this because the W3 said that it's time to do so. My point is that support for prefixed CSS properties should not be available in stable releases at all. What they should have done from the beginning (and from other comments seems it will be done in the future) is to enable experimental prefixed CSS properties only in dev builds (to demonstrate to the W3C working group the feasibility of those new properties) and remove such properties from stable releases. In this way the stable releases will have _only_ W3C approved prefixes, not the current mess of draft + CR + TR support.