W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2018

Re: [csswg-drafts] [web-animations-2] AnimationWorklet integration - using GroupEffect and allowing control of localTime

From: Brian Birtles via GitHub <sysbot+gh@w3.org>
Date: Mon, 02 Jul 2018 00:18:26 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-401643351-1530490705-sysbot+gh@w3.org>
Sorry for the delay in responding here.

> ```webidl
> partial interface AnimationEffect {
>    [Exposed=AnimationWorklet] attribute double localTime;
> }
> ```

We already have the `getTiming().localTime` member. I wonder how this should interact. Should we set it through `updateTiming()` instead?

> This is consciously a conservative API. In particular:
> 
> *  Does not expose any constructor. The actual construction of group effect is done internally.

Previous TAG feedback has been that we should not have objects that get created by the platform without constructors.

> * Does not allow nesting worklet group effects. So there can only be one nesting levels.

This seems reasonable (assuming we have a natural means of extending this to do nesting in future).

> To implement something like this we need to so some ground work in Blink for general group effects. This should also give us valuable implementation feedback on GroupEffects in general beyond their
> application with worklet animations.

Sounds great.

> **Note:** I choose to use a readonly sequence<AnimationEffect> instead of of per this issue

This seems reasonable to me but we'll need to think about how we expect this to be updated in future.

-- 
GitHub Notification of comment by birtles
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2071#issuecomment-401643351 using your GitHub account
Received on Monday, 2 July 2018 00:18:29 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:30:53 UTC