Skip to content

Commit 3c1cd1b

Browse files
authored
AnimationWorklet Editorial cleanups (w3c#864)
- Fix make file (Issue w3c#852) - Update issue links to point to the write repository - Update animation threading image to be cleaner - Update link to explainer and add link to principles document - Mention web animations extensibility in intro - Add empty privacy and security sections - Make web animations section non-normative - Remove outdated issue on reverse/playbackRate - Update GroupEffect to mention delta spec
1 parent 13e5ec9 commit 3c1cd1b

File tree

3 files changed

+33
-20
lines changed

3 files changed

+33
-20
lines changed

css-animationworklet/Makefile

+3-3
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@
44
#
55
# Use "make REMOTE=1" to use remote bikeshed
66

7-
SOURCEFILE=index.bs
8-
OUTPUTFILE=index.html
9-
PREPROCESSOR=bikeshed.py
7+
SOURCEFILE=Overview.bs
8+
OUTPUTFILE=Overview.html
9+
PREPROCESSOR=bikeshed
1010
REMOTE_PREPROCESSOR_URL=https://api.csswg.org/bikeshed/
1111

1212
all: $(OUTPUTFILE)

css-animationworklet/Overview.bs

+29-16
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ Title: CSS Animation Worklet API
33
Status: ED
44
Group: houdini
55
ED: https://drafts.css-houdini.org/css-animationworklet-1/
6-
Shortname: css-workletanimation
6+
Shortname: css-animationworklet
77
Level: 1
88
Abstract:
99
Editor: Majid Valipour, majidvp@google.com
@@ -89,12 +89,17 @@ urlPrefix: https://wicg.github.io/scroll-animations/#; type: dfn
8989
<pre class=biblio>
9090
{
9191
"explainer": {
92-
"href": "https://github.com/WICG/animation-worklet/blob/gh-pages/README.md",
92+
"href": "https://github.com/w3c/css-houdini-drafts/blob/master/css-animationworklet/README.md",
9393
"title": "Animation Worklet Explainer",
94-
"status": "CR",
95-
"publisher": "WICG",
9694
"deliveredBy": [
97-
"https://github.com/WICG/animation-worklet//"
95+
"https://github.com/w3c/css-houdini-drafts"
96+
]
97+
},
98+
"principles": {
99+
"href": "https://github.com/w3c/css-houdini-drafts/blob/master/css-animationworklet/principles.md",
100+
"title": "Animation Worklet Design Principles and Goals",
101+
"deliveredBy": [
102+
"https://github.com/w3c/css-houdini-drafts"
98103
]
99104
}
100105
}
@@ -104,8 +109,9 @@ Introduction {#intro}
104109
=====================
105110
<em>This section is not normative.</em>
106111

107-
This document introduces a new primitive for creating scroll-linked and other high performance
108-
procedural animations on the web. For details on the rationale and motivation see [[explainer]].
112+
This document introduces a new primitive that provides extensibility in web animations and enables
113+
high performance interactive procedural animations on the web. For details on the rationale and
114+
motivation see both [[explainer]] and [[principles]].
109115

110116
The <a>Animation Worklet</a> API provides a method to create scripted animations that control a set
111117
of <a>animation effects</a>. The API is designed to make it possible for user agents to run such
@@ -114,14 +120,11 @@ thread.
114120

115121
Relationship to the Web Animations API {#relationship-to-web-animations}
116122
------------------------------------------------------------------------
123+
<em>This section is not normative.</em>
117124

118125
Animations running inside an <a>Animation Worklet</a> execution context expose the {{Animation}}
119126
interface from the Web Animations specification on the main javascript execution context. This means
120-
they can be controlled and inspected from main thread using many of the Web Animation APIs. However
121-
Animation Worklet animations follow a different timing model that enables them to be script-driven,
122-
stateful, and runnable in a parallel worklet execution context. As such Web Animation APIs that seek
123-
or alter the input time (reverse, finish, etc.) have different semantics for Animation Worklet
124-
animations.
127+
they can be controlled and inspected from main thread using the same Web Animation APIs.
125128

126129

127130
Threading Model {#threading-model}
@@ -683,7 +686,7 @@ Here are a few implications of the above semantics:
683686
may return stale information, in the case where the <a>animator instance</a> is running in a
684687
parallel execution context.
685688

686-
Issue(63): Come with appropriate mechanism's for <a>animator instance</a> to get notified when its
689+
Issue(811): Come with appropriate mechanism's for <a>animator instance</a> to get notified when its
687690
animation currentTime is changing e.g., via reverse(), finish() or playbackRate change. So that
688691
it can react appropriately.
689692

@@ -762,7 +765,7 @@ is called, then <a>set animator instance of worklet animation</a> given |worklet
762765
Timeline Attachment {#timeline-attachment}
763766
-------------------
764767

765-
Issue(61): Define semantics of attachment and detachment.
768+
Issue(810): Define semantics of attachment and detachment.
766769

767770
ScrollTimeline {#scroll-timeline}
768771
---------------------------------
@@ -817,8 +820,8 @@ action that corresponds to the first matching condition from the following:
817820
</div>
818821

819822
Issue(w3c/csswg-drafts#2071): The above interface exposes a conservative subset
820-
of GroupEffect proposed as part of web-animation-2. Once that is available we
821-
should switch to it.
823+
of GroupEffect proposed as part of web-animation-2. We should instead move this
824+
into a delta spec against the web-animation.
822825

823826

824827
Effect Stack and Composite Order {#effect-stack-composite-order}
@@ -829,6 +832,16 @@ worklet animation does not have a specific <a>animation class</a> which means it
829832
composite order as other Javascript created web animations.
830833

831834

835+
Security Considerations {#security-considerations}
836+
==================================================
837+
838+
There are no known security issues introduced by these features.
839+
840+
Privacy Considerations {#privacy-considerations}
841+
================================================
842+
843+
There are no known privacy issues introduced by these features.
844+
832845
Examples {#examples}
833846
====================
834847

0 commit comments

Comments
 (0)