W3C home > Mailing lists > Public > www-style@w3.org > January 2014

Re: Ordering in 'animation' shorthands

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 22 Jan 2014 18:19:03 -0800
Message-ID: <CAAWBYDBEPG7hZbcy49B6PkvLUOwno8kKV_Uhagfz_4KsZUR2ag@mail.gmail.com>
To: "L. David Baron" <dbaron@dbaron.org>
Cc: www-style list <www-style@w3.org>
On Wed, Jan 22, 2014 at 5:19 PM, L. David Baron <dbaron@dbaron.org> wrote:
> Fixed in https://dvcs.w3.org/hg/csswg/rev/68697748c5cc .


> I left some ambiguity in the required serialization, but we might
> want to tighten that as well.  I'd prefer to just require that the
> serialization always output all the keywords (as Gecko does) since
> it's a pain to determine whether disambiguation is needed, and
> consistent behavior seems less likely to trip up authors who depend
> on the serialization behaving in a particular way.

We don't *need* to serialize every property value; the only real
requirement is that if the animation-name is a valid value for one of
the other sub-properties, that other sub-property must be included in
the serialization and must be placed before the animation-name.
(Similarly, if there's a non-default delay, the duration must be
serialized, and must be placed before it.)

I wouldn't mind requiring everything to be serialized, though.

> (I'd also note I found some interesting slightly-out-of-date-Blink
> bugs while testing its parsing and serialization of the 'animation'
> shorthand, such as the value parsed from 'backwards 3s forwards'
> being serialized as 'forwards 3s backwards'.)

I reported this, and suggested how we could test for it.

Received on Thursday, 23 January 2014 02:19:50 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:36 UTC