- From: Sylvain Galineau <sylvaing@microsoft.com>
- Date: Wed, 1 Aug 2012 19:27:13 +0000
- To: Tab Atkins Jr. <jackalmage@gmail.com>, François REMY <fremycompany_pub@yahoo.fr>
- CC: Rik Cabanier <cabanier@gmail.com>, Sebastian Zartner <sebastianzartner@gmail.com>, Julien Dorra <juliendorra@juliendorra.com>, "www-style@w3.org" <www-style@w3.org>
[Tab Atkins Jr.:] > The fact that they currently ignore them actually means that we probably > can't change our behavior - people may have left properties in their > animations and are now accidentally depending on them not working. > Indeed; it's relatively easy to find books, samples and demos that use the shortcut of transitioning on 'all' vs. specifying the properties to animate. Except, of course, 'all' really means 'all the things current browsers animate'. Animations may be less prone to this broad issue since each keyframe rule must specify the properties that animate but 'enabling' the animation of display may still have unexpected consequences. > However, the use-case is very valid. Yes. > I think we should be able to solve > this with a new timing function that works for all properties (and define > that the others only work for "animatable" values) - > discrete(<percentage>). The percentage indicates at what point in the > time it should flip from the start value to the end value. I think that is one possible approach.
Received on Wednesday, 1 August 2012 19:28:12 UTC