[web-animations] miscellaneous feedback

I was searching through /TR/2015/ and found [1].

Please note that this isn't a review. I'm currently reviewing another
document and this popped up during that review. I'll review this
document sometime after it is announced by Notifier.

> 3.5.15. Cancelling an animation

Please use en-US single -eling/-eled (canceling/canceled), as in other
w3 documents [2]:

Mar 19, 2015 - [3] UI Events (formerly DOM Level 3 Events)
> 5.6.2 Composition Event Order;
> 5.6.3 Handwriting Recognition Systems;
> 5.6.4 Canceling Composition
;
> 5.6.5 Key Events During ...

Jan 15, 2015 - [4] IndieUI: Events 1.0
> IndieUI: Events focuses on granular user interface interactions such as scrolling the view, canceling an action, changing the value of a user ...

May 6, 2015 - [5] 5 User interaction | HTML 5.1 - World Wide Web Consortium
> If the current drag operation is " none " (no drag operation), or,
> if the user ended the drag-and-drop operation by canceling it (e.g. by hitting the ...

> Two features characterise the Web Animations timing model: it is stateless and it is hierarchical .

please use en-us -ize

> When doing so, the current time will not progress but the animation will act as if it had been paused at the seeked [sp] time.

the past tense of (v) to seek is sought

> These states and their useage [sp] within the model are summarised [sp] as follows:

usage
-ize (as above)

> After one iteration, the iteration time is 0, but after two iterations (and thereonwards [sp]),

insert at least a space after `there`

> the iteration time is equal to the iteration duration due to the special behavior defined when an animation effect fills.

> There used to be a step here which seemed to be adding special handling for filling when the effect ends on a repeat boundary but it seems like that is taken care of by the calcuation [sp] of iteration time and current iteration.

> Conversely, in other situations such as when modelling [sp] a discrete change, a smooth transition is undesirable and instead it is necessary for the animation effect to progress in a series of distinct steps.

-eling as above

> The timing functions produced by each of the keyword values associated with cubic Béier [sp] timing functions accepted by the easing member of the AnimationEffectTiming interface member from the programming interface.

> For animation behaviors that do not define a specific procedure for distance computation or which are defined as not paceable [sp],

This isn't a word (~10k hits on Google, no dictionary references).

> the distance computation procedure is simply distance = 1.

> This process is called compositing and is based on establishing an effect stack for each property targetted [sp] by an in effect animation effect.
The results of keyframe effects targetting [sp] the same property are
composited together using an effect stack .

-eted/-eting as above

>     Unpauses [sp] the animation and rewinds if it has finished playing using the procedure to play an animation for this object.

Please use (v) resume in of un- + (v) pause.

> The internal representation of time values is implementation dependant [sp] however,

-dent

> it is RECOMMENDED that user agents be able to represent input time values with microsecond precision so that 0.000001 is distinguishable from 0.0.

> Deferred the animation effect-specific playback rate since it was considered to be not particularly useful without group effects and potentially confusing (since animationss [sp] also have an animation playback rate).



[1] http://www.w3.org/TR/2015/WD-web-animations-1-20150707/
[2] https://www.google.ca/search?q=inurl:http:%2F%2Fwww.w3.org%2FTR%2F2015+%22canceling%22
[3] http://www.w3.org/TR/2015/WD-uievents-20150319/
[4] http://www.w3.org/TR/2015/WD-indie-ui-events-20150115/
[5] http://www.w3.org/TR/2015/WD-html51-20150506/editing.html

Received on Tuesday, 25 August 2015 15:25:13 UTC