- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 25 Jan 2012 08:17:36 -0800
- To: Lea Verou <leaverou@gmail.com>
- Cc: jwl@worldmusic.de, Aryeh Gregor <ayg@aryeh.name>, www-style@w3.org
On Wed, Jan 25, 2012 at 4:19 AM, Lea Verou <leaverou@gmail.com> wrote: > FWIW I think there shouldn't be a list at all. It's a maintenance nightmare > to have to update the spec every time a new property is defined. As long as > it defines how each value type is interpolated, their combination and > potential exceptions, I never got why an all inclusive list is needed. A > list of a few examples, sure, but a list that has to include every CSS > property?! In general, the list includes everything that was "mature" at the time Transitions was created. We now have an "Animatable" line in the propdef tables in our spec template, so all CSS3 specs should include their animation information as part of their property descriptions, and the list in Transitions can just deal with 2.1 properties. ~TJ
Received on Wednesday, 25 January 2012 16:18:26 UTC