Re: Suggestion for generic CSS vendor prefix

On Mon, Mar 22, 2010 at 2:21 PM, Robert O'Callahan <> wrote:
> If there is a problem we need to solve here, it's that for some properties
> there's a long gap between the syntax and behavior freezing and the spec
> going into CR, at which time unprefixed implementations are officially
> allowed. Fixing that requires a change in policy and/or process.

Indeed, THIS is where we can help authors out.  A unified draft prefix
will *not* do any good, and will instead be painful to authors who
don't realize that browsers may implement the property differently at
first, or may implement different drafts.  (The suggestion of using
draft, draft2, draft3, etc. doesn't help here, because different
browsers may still end up with different behavior based on the same
draft, before interop problems are discovered and clarified.)

Though it wasn't in this particular email, I find it darkly amusing
that a common example of a ridiculous situation that would be fixed by
a single draft prefix is border-radius, when Firefox's behavior for
-moz-border-radius is *not* what the current draft says.


Received on Monday, 22 March 2010 22:08:39 UTC