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

Re: [css-animations] More ambiguity questions with the animation shorthand

From: Sylvain Galineau <galineau@adobe.com>
Date: Wed, 28 May 2014 00:23:11 +0000
To: Tab Atkins Jr. <jackalmage@gmail.com>
CC: "<www-style@w3.org>" <www-style@w3.org>
Message-ID: <BCC96E83-BE94-43D8-BBFE-6EA5DB735526@adobe.com>

On May 27, 2014, at 2:10 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote:

> At the F2F, we agreed to some principles for handling <custom-ident>
> when it can't be disambiguated positionally, based on the 'animation'
> shorthand.  Basically, values should be assigned to the longhands
> greedily, with the <custom-ident> longhand having the lowest priority
> when claiming a value.  That way, "animation: ease-in linear;" gets
> parsed with a timing-function or "ease-in" and a name of "linear".
> 
> This works fine when the value spaces that <custom-ident> might clash
> with contain *only* idents, but it's less clear what to do when they
> can contain other things, like functions.  In particular, how should
> we parse "animation: ease-in steps(2);"?  Should we greedily assign
> ease-in to timing-function, and then fail to parse the property when
> we hit the function?  Or should we allow new values to reassign
> things, so we get a name of "ease-in" and a timing-function of
> "steps(2)"?
> 
> The latter is basically the list-style behavior, where you can't tell,
> upon seeing a "none", whether it should be assigned to list-style-type
> or list-style-image until you see the rest of the property.
> 
> ~TJ
> 
Keeping track of animation shorthand parsing feedback in https://www.w3.org/Bugs/Public/show_bug.cgi?id=14805
Received on Wednesday, 28 May 2014 00:23:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:51:27 UTC