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

Re: [css3-animations] Multiple animations affecting the same property

From: Sebastian Markbåge <sebastian@calyptus.eu>
Date: Thu, 22 Sep 2011 17:17:35 +0200
Message-ID: <CAEfn7zPan=_SjbyddmGi4ygz3DgHtQhwNFx5e6eO4RfHKxYiqw@mail.gmail.com>
To: Øyvind Stenhaug <oyvinds@opera.com>
Cc: www-style@w3.org
On Thu, Sep 22, 2011 at 5:14 PM, Øyvind Stenhaug <oyvinds@opera.com> wrote:

> On Thu, 22 Sep 2011 16:36:15 +0200, Øyvind Stenhaug <oyvinds@opera.com>
> wrote:
>
>  http://dev.w3.org/csswg/css3-**animations/#animations<http://dev.w3.org/csswg/css3-animations/#animations>
>>
>> "In the case of multiple animations specifying behavior for the same
>> property, the animation defined last will override the previously defined
>> animations."
>>
>> I found this rather unclear. It should probably say something like
>>
>> "If at one point in time there are multiple animations specifying behavior
>> for the same property, the animation whose name occurs last in the value of
>> 'animation-name' will override the other animations at that point."
>>
>
> Actually, might need to qualify that sentence further, since it should
> presumably only be about animations that actually apply (are associated with
> valid keyframes).
>
>
> --
> Øyvind Stenhaug
> Core Norway, Opera Software ASA
>
>
(1) Additionally, it should be defined what should happen if one animation
defines properties for part of an animation. E.g. what happens if a
last-named animation specifies a property at 50% but not before that? Is it
overriding the other animations at 0% or 50%?

(2) Perhaps off-topic, some properties are useful to combine rather than
override. Transforms in particular. For transforms it would make more sense
to multiply the transform of all defined animations, in the order in which
they where defined.

A real use case for this is to use timing functions to move along a curve.
http://lists.w3.org/Archives/Public/www-style/2011Sep/0295.html
Received on Thursday, 22 September 2011 15:18:05 GMT

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