RE: vendor prefixes: co-cascading

I don't see the problem with -draftX- prefixes. Until a consensus has been reached, the property should not be included in RTM builds anyway. That means there will be no problem about an old draft getting used too much on the web. The purpose of -draft prefixes is to have interoperable demo on unstable features for browsers that supports the same property without having to use as many prefixes as browsers. Browsers could also support more than one implementation for testing purposes.

Since a property could be implemented in RTM UAs only if it's possible to use interoperable code between them for most common scenarios, it should be implemented prefix-less in RTM. Non interoperable scenarios will then be worked out but should not cause too much pain.

François