- From: Robert Flack via GitHub <sysbot+gh@w3.org>
 - Date: Thu, 15 Aug 2019 15:35:47 +0000
 - To: public-houdini-archive@w3.org
 
flackr has just created a new issue for https://github.com/w3c/css-houdini-drafts:
== [css-animationworklet] Move interface idls close to definitions for easier readability. ==
The [Animation Worklet](https://drafts.css-houdini.org/css-animationworklet/#animation-worklet-desc) section introduces the `CSS.animationWorklet` interface and the AnimationWorkletGlobalScope, however the `idl` for paintWorklet follows the introduction of the global scope, and the `idl` for AnimationWorkletGlobalScope is in a [later section](https://drafts.css-houdini.org/css-animationworklet/#registering-animator-definition).
I think for readability, similar to [Paint Worklet](https://www.w3.org/TR/css-paint-api-1/#paint-worklet) the idl for each should follow their introduction in the [Animation Worklet](https://drafts.css-houdini.org/css-animationworklet/#animation-worklet-desc) section.
i.e.
```
Animation Worklet {#animation-worklet-desc}
===========================================
<dfn>Animation Worklet</dfn> is a {{Worklet}} responsible for all classes related to custom
animations. The worklet can be accessed via {{animationWorklet}} attribute.
The {{animationWorklet}}'s <a>worklet global scope type</a> is {{AnimationWorkletGlobalScope}}.
<idl for animationWorklet>
{{AnimationWorkletGlobalScope}} represents the global execution context of {{animationWorklet}}.
<idl for AnimationWorkletGlobalScope>
```
Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/926 using your GitHub account
Received on Thursday, 15 August 2019 15:35:53 UTC