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

Re: renaming "Animatable:" to "Interpolation:" in property definition tables

From: Garrett Smith <dhtmlkitchen@gmail.com>
Date: Fri, 22 May 2015 22:13:56 -0700
Message-ID: <CABZUbM0S3o7xaDF3FLX5TOMR3szNhvNLW62m5MnWrZjXHsEQ8Q@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: "L. David Baron" <dbaron@dbaron.org>, www-style list <www-style@w3.org>
It can be better.

Switching `display` or `visibility` in the middle of an animation is
not something I've ever wanted. It's useful to do switch it either at
the first frame or at the end. When transitioning to computed values
such as display: "none" or visibility: "hidden" or "collapse", the
change should occur at the end. But in cases where the computed value
to transition to is a display other than none, or visibility other
than "hidden" | "collapse", most of the time, it's best done in the
beginning, where it's changing the display from "none" and then
running the adjustable properties (color, font-size, etc) in that new
display value.



On 5/22/15, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> On Fri, May 22, 2015 at 12:56 PM, L. David Baron <dbaron@dbaron.org> wrote:
>> In [1] and [2] the working group resolved that both animations and
>> transitions should work on properties that cannot be interpolated,
>> and these properties should switch when the timing function crosses
>> 50%.  (This is particularly useful with the step-start and step-end
>> timing functions.)
>>
>> Given this resolution, I think it no longer makes sense for the line
>> in the property definition table to be "Animatable:", as I suggested
>> on IRC in [1].
>>
>> I'd like to change "Animatable:" to "Interpolation:", and change the
>> common "no" value to "discrete" or "in steps" or something similar.
>>
>> This is basically an editorial change that follows from the existing
>> resolutions in [1] and [2], but since it affects multiple
>> specifications I wanted to give people a chance to comment.
>
> I agree with this change.  I support "discrete" as the initial value.
> I can switch Bikeshed over to accepting either value, so there's no
> change needed for specs that either omitted the line entirely (which
> gives you the default "none" value) or specified a non-none value.
> Only specs that currently have an explicit "Animatable: none" would
> have to be changed, unless I make Bikeshed magically translate that
> into the preferred default value. ^_^
>
> ~TJ
>
>


-- 
Garrett
@xkit
ChordCycles.com
garretts.github.io
personx.tumblr.com
Received on Saturday, 23 May 2015 05:14:26 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:31 UTC