W3C home > Mailing lists > Public > www-style@w3.org > November 2012

Re: [css3-animations] Ability to have "adjacent" keyframes / "instantaneous" interpolations

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 20 Nov 2012 13:57:45 -0800
Message-ID: <CAAWBYDAm=49Ud1r-v=F=qhqqHgQvb0xzh6B7hKKnbXZ0uMkY1g@mail.gmail.com>
To: Sylvain Galineau <sylvaing@microsoft.com>
Cc: www-style list <www-style@w3.org>
On Tue, Nov 20, 2012 at 1:55 PM, Sylvain Galineau
<sylvaing@microsoft.com> wrote:
> [Tab Atkins Jr.:]
>> The reason I call it hacky is not its lack of discoverability (though
>> that's a problem), but because it relies on the author guessing at an
>> appropriate epsilon to add to the keyframe time.  If they guess too large,
>> it might be detectable in some cases as a small lag before the property
>> starts animating again.  If they guess too small, they'll run into impl
>> precision limits and might accidentally collapse it into the same time,
>> which has a bad effect.  (That is, "50%" and "50.000001%"
>> might be the same time, depending on impl limits.)
>>
>> We generally try to avoid doing things like this, where rounding behavior
>> is potentially exposed to authors.
>>
> Yes, we would still want a keyword that indicates the next keyframe rule
> defines, well, the next frame in the animation.
>
> Somehow allowing multiple keyframe rules with the same selector would not
> be backward-compatible and I think it should really be an explicit selector
> value or function.
>
> May not make this level but I'll add it to the bug list.

That's exactly what I was suggesting, so thank you.  ^_^  I'm fine
with it not hitting this level - it's low priority.

~TJ
Received on Tuesday, 20 November 2012 21:58:33 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:02 GMT