W3C home > Mailing lists > Public > www-style@w3.org > November 2011

Re: Unprefixing CSS properties

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 16 Nov 2011 14:41:45 -0800
Message-ID: <CAAWBYDA0-ynvHrdJbceqnd7r88F82qKGBkwsaFr9eqpfP96dDg@mail.gmail.com>
To: Ojan Vafai <ojan@chromium.org>
Cc: Brian Manthos <brianman@microsoft.com>, "robert@ocallahan.org" <robert@ocallahan.org>, Henri Sivonen <hsivonen@iki.fi>, "www-style@w3.org" <www-style@w3.org>
On Wed, Nov 16, 2011 at 2:35 PM, Ojan Vafai <ojan@chromium.org> wrote:
> Stated differently, I read it as saying the following: When we get to a
> state that some features are CR-ready and others are not, we should strip
> the non-CR-ready features and put them in the next version of that module
> and bring the CR-ready features to CR.
> That seems very different to me than marking individual features as stable.
> Mainly, it's a ton of busy work.

People keep saying that.  It's really not.

It's *more* work than just putting a note in a spec that says "hey,
this part is stable", sure.  But it's not a huge deal.  We have to do
the LC work to bring it to CR anyway, and making a new spec for the
next level isn't hard.

~TJ
Received on Wednesday, 16 November 2011 22:42:34 GMT

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