W3C home > Mailing lists > Public > www-style@w3.org > February 2012

Re: wading into the Prefix morass...

From: Brad Kemper <brad.kemper@gmail.com>
Date: Mon, 20 Feb 2012 15:07:33 -0800
Message-Id: <04D09B13-860B-4564-9A15-14DDBE0C8DBA@gmail.com>
Cc: David Singer <singer@apple.com>, "www-style@w3.org Style" <www-style@w3.org>
To: Brian Manthos <brianman@microsoft.com>
On Feb 20, 2012, at 11:56 AM, Brian Manthos <brianman@microsoft.com> wrote:

>> This is what led to me wondering (a few emails ago) if we could
>> usefully use draft-specific prefixes for features, and only change
>> the prefix if the parsing had to change.
> 
> On one specific point, just an observation...
> 
> Parsing changes aren't the only spec change that introduces incompatibility.
> 
> Draft A:  0 deg points right
> -draft-linear-gradient(10deg, red, blue);
> 
> Draft B:  0 deg points up
> -draft-linear-gradient(10deg, red, blue);
> 
> 
> I can give you specifics on which draft versions if it's actually useful for you.

Exactly. There were also times when the same blur radius produced very, very different results between -webkit-box-shadow and -moz-box-shadow. As an author, I was able to make the results more consistent by giving different values to each. Then by the time they were unprefixed in CR, we had decided on a more consistent way to determine the results of blur.
Received on Monday, 20 February 2012 23:08:01 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:50 GMT