- From: Dean Jackson <dino@apple.com>
- Date: Tue, 02 Aug 2011 22:48:11 -0700
- To: Brad Kemper <brad.kemper@gmail.com>
- Cc: Alan Gresley <alan@css-class.com>, Rik Cabanier <cabanier@gmail.com>, Jonathan Snook <jonathan@snook.ca>, "www-style@w3.org" <www-style@w3.org>
On 02/08/2011, at 8:58 PM, Brad Kemper wrote: > On Aug 2, 2011, at 5:25 PM, Dean Jackson <dino@apple.com> wrote: > >> The spec could say that percentages < 100 for non-continuous properties are the starting state. So in the example above, the animation would be 'block' for four seconds up to the last frame where it would immediately change to 'none'. > > I thought we had agreed to that sort of thing at the f2f in Mountain View Mozilla last year. Yes. >> There is another alternative which may be too hard to specify, which is that UAs might crossfade the rendering of the begin and end states. > > That would be great; throw in some wipes and other effects too. That can always be added in to a later version of the spec. > >> The problem is when you want other things to animate at the same time. > > Why is that a problem? I imagine something like a checkerboard wipe would scale and move with the bounding box of the element. It's only a problem if you're animating multiple properties on the same element, one of which can only be done via a cross-fade. In that case you probably drop back to cross-fade on everything. Not a big deal. Dean
Received on Wednesday, 3 August 2011 05:48:47 UTC