On 2016/03/09 8:59, Tab Atkins Jr. wrote:
If we think the back-compat isn't bad, tho, I do like this the best.
We'd then get to add a "step" keyword, too, which is a shorthand for
"steps(1)", and gives the default "non-animatable value" behavior.
I couldn't work out how to search GitHub for thi
s place, while "equal"
doesn't but actually influence the length of each segment, so it's a bit
odd. Still, I think it's ok.
If we can't find a suitable keyword to stick into steps(), then another
option is to mint a completely separate function (e.g. stagger(),
On 2012/12/21 3:46, Tab Atkins Jr. wrote:
On Wed, Dec 19, 2012 at 6:40 PM, L. David Baron wrote:
On Wednesday 2012-12-19 10:29 -0800, Tab Atkins Jr. wrote:
I propose another steps value: step-mid. It splits the animation curve
into n segments, makes the first n-1 do step-end behavior, and leav
ors>
<http://linkedin.com/in/rachelnabors>
--------
Curator of Web Animation Weekly <http://www.webanimationweekly.com>
On Wed, Nov 25, 2015 at 6:40 PM Brian Birtles mailto:bbirt...@mozilla.com>> wrote:
Hi,
Web Animations defines Animatable.getAnimations() (where Animatable is
implemented by Element and a forthcoming PseudoElement interface) and I
think we've agreed to add Document.getAnimations() as well.[1]
I've found two problems with the first method which I'm going to call
Element.getA
On 2015/11/26 8:36, Brian Birtles wrote:
If that's the case, maybe the original example should preserve
"iterations = -1" for consistency and authors just need to be careful to
always query getComputedTiming() if they want sensible results?
And just to argue the opposite side,
Hi,
(CC'ing www-style since the may be some precedent from CSSOM we can
apply here.)
Web Animations currently says that if I do the following:
var anim = elem.animate({ opacity: 0 },
{ duration: 1000, iterations: -1 });
I'll see the following:
anim.effect.timing
Hi Kevin,
Thanks for your mail.
On 2015/11/25 13:52, Kevin Doughty wrote:
element.animate(animation [, name]);
element.animate(effect, timing [, name]);
This would permit usage patterns that avoid your stated problems
I'm not really sure that adding optional names is going to solve this.
Hi,
We have a difficulty in Web Animations with regards to object lifetimes
for animations that fill forwards. The trouble is one can do the
following:
elem.addEventListener('click', evt => {
evt.target.animate({ opacity: [ 0, 1 ] },
{ duration: 500, fill: 'forwards'
On 2015/10/09 7:51, Shane Stephens wrote:
Any thoughts?
This seems like a really good idea.
As an extra point - we don't need to solve custom animations (onsample
effects that modify the document) until L2, so we don't need to think
about this right now - but if we said that animations wi
On Sat, Oct 3, 2015 at 1:21 AM, Domenic Denicola wrote:
> Anne's questions are interesting and worth answering. For example, which of
> these properties are typically held in memory already, versus which would
> require some kind of computation---the former usually are better as
> properties, a
On Sat, Oct 3, 2015 at 1:14 AM, Anne van Kesteren wrote:
> On Thu, Oct 1, 2015 at 4:23 AM, Brian Birtles wrote:
>> I'd like to change this API, probably to one of the following (listed
>> roughly in order of preference). I wonder if anyone else has an opinion
>> on t
(CC-ing public-webapps and www-style since I think this API needs more
eyes on it)
Hi,
Web Animations currently has the following API[1]:
interface AnimationEffectReadOnly {
readonly attribute AnimationEffectTimingReadOnly timing;
readonly attribute ComputedTimingProperties comp
Hi,
Summary:
* I think we should drop AnimationTimeline.getAnimations()
* I think we should add Document.getAnimations()
I've been working on implementing the Web Animations model in Gecko and
I've made a few observations:
1. document.timeline.getAnimations() is not really useful
If you wa
On 2015/09/05 4:06, Rachel Nabors wrote:
Been seeing a need for a global playback rate for animations. Talking
with accessibility experts about older users often needing slower
animations makes me think this is something individual sites if not
browsers themselves would like to offer user control
Hi Amelia,
Thank you for writing this up! As a high-level comment, I like it! We've
discussed this feature a few times and there's even an issue in the spec
describing something quite similar to this.[1]
The main resistance, however, has been to the list of numbers in the
syntax. Some were con
Hi Kari,
On 2015/07/17 15:31, Kari Pihkala wrote:
Out of curiosity, do we even need the notion of sequence numbers? Or can
animations be regarded as belonging to a list or array structure that
can be enumerated and manipulated with familiar push/pop/insert/append
APIs? (Apologies if this has bee
On 2015/07/16 16:50, Kristopher Giesing wrote:
I was thinking that something like this is probably the best solution.
(I've had some nightmarish experiences with z-order, so I'm all for
avoiding that as a paradigm.)
Out of curiosity, do we even need the notion of sequence numbers? Or can
anima
Hi,
Just following up on this thread, Shane and I discussed this a bit on
IRC yesterday and we wonder if we should push ahead with adding the
ability to tweak priorities soon-ish.
A few points we discussed:
* "Priority" may be confused with CSS prioritization. From here on we
will refer to "c
Hi Shane,
I definitely agree start-time scheduling is problematic. I was just
interested in why creation-time ordering is better, particularly as
opposed to first-transition-from-idle (let's call it FTFI).
The first two points of your mail were about the problems with TFI which
I agree are w
On 2015/07/09 11:30, Shane Stephens wrote:
I wonder if this proposal is a little bit odd in that we have the
following two cases:
a) var anim = new CSSAnimation(...);
anim.play();
b) elem.style.animation = "...";
var anim = elem.getAnimations()[0];
el
Hi David,
On 2015/07/14 5:58, David Dailey wrote:
I'm a bit confused (still). In looking through the document, it looks
as though almost everything that looks like "traditional" animation
(in terms of the 15 year old thing that people used to call a "W3C
Standard" -- I finally understand W3C's u
On 2015/07/01 8:41, Brian Birtles wrote:
I'm not really sure what's best:
a) Be consistently synchronous and force authors to be careful about the
order in which they perform operations;
b) Be consistently asynchronous and possibly produce some surprising
results where calling ca
On 2015/07/09 6:50, Shane Stephens wrote:
On Fri, Jul 3, 2015 at 12:21 PM Brian Birtles mailto:bbirt...@mozilla.com>> wrote:
Also, I think we need to clarify when these sequence numbers are
updated. Presumably changes to tree order prior to disassociating the
animations are res
On 2015/07/01 15:59, Brian Birtles wrote:
On 2015/06/18 16:24, Brian Birtles wrote:
Dear all,
The editors of the Web Animations specification would like to publish
another Working Draft based on the current Editor's Draft.[1] A (rather
long) list of changes is included at the end of this
On 2015/07/02 15:10, Shane Stephens wrote:
I guess either you're suggesting:
a) Updating animation properties triggers a global sequence number
rewrite (I hope this isn't the case), or
b) Script-animations and CSS animations share the same source of
sequence number
On 2015/06/23 8:57, Shane Stephens wrote:
An alternative proposal:
CSS animations use sequence number as priority, and are created in tree-
and list- order. CSS Animations are still prioritized absolutely above
script animations (there are two lists). Changing an animation-name
property triggers
On 2015/06/18 16:24, Brian Birtles wrote:
Dear all,
The editors of the Web Animations specification would like to publish
another Working Draft based on the current Editor's Draft.[1] A (rather
long) list of changes is included at the end of this mail.
We plan to publish on July 2 unless
c-fx/2015AprJun/0046.html
On Wed, Jul 1, 2015 at 12:07 PM Brian Birtles mailto:bbirt...@mozilla.com>> wrote:
Hi,
Currently, Web Animations defines a 'name' attribute on
KeyframeEffectReadOnly. I think this belongs on Animation.
Rationale: We plan
Hi,
Currently, Web Animations defines a 'name' attribute on
KeyframeEffectReadOnly. I think this belongs on Animation.
Rationale: We plan to define CSSAnimation.animationName and
CSSTransition.transitionProperty largely for the purpose of identifying
particular animations running on an eleme
should just go back to (a).
Best regards,
Brian
On Mon, Jun 29, 2015 at 10:58 PM, Brian Birtles mailto:bbirt...@mozilla.com>> wrote:
On 2015/06/30 13:21, Brian Birtles wrote:
Hi,
I'm currently speccing finish/cancel events for animations and I
think
[ Sorry for the delay here, I just discovered these notes in the
Etherpad and I don't appear to have ever sent them to the list. ]
Web Animations minutes, 28 May 2015
Present: Doug, Mike, Shane, Brian
Archived etherpad:
https://web-animations.etherpad.mozilla.org/ep/pad/view/ro.92487irtSfEow/
On 2015/06/30 13:21, Brian Birtles wrote:
Hi,
I'm currently speccing finish/cancel events for animations and I think
it makes sense to dispatch finish events and also update the finished
promise in a separate task.
I was thinking of applying similar handling to the cancel event
includin
Hi,
I'm currently speccing finish/cancel events for animations and I think
it makes sense to dispatch finish events and also update the finished
promise in a separate task.
The would mean that something like:
var anim = elem.animate({...}, 3000);
anim.currentTime = 5000;
anim.currentTi
Hi Glen,
Sorry, I'm just now catching up on your feedback.
On 2015/06/25 20:58, Glen Huang wrote:
Also curious about two things:
1. Is zero duration, forwards filled, single keyframe effect valid and
fills with the keyframe?;
```
new KeyframeEffect(el, {position: "static"}, {fill: "forwards"})
On 2015/06/22 16:57, Shane Stephens wrote:
An alternative proposal:
CSS animations use sequence number as priority, and are created in tree-
and list- order. CSS Animations are still prioritized absolutely above
script animations (there are two lists). Changing an animation-name
property triggers
On 2015/06/22 14:14, Brian Birtles wrote:
On 2015/06/22 13:10, Shane Stephens wrote:
One concern I have is that currently text order (or creation order) is
inviolate which makes it easy to reason about; but that might be
outweighed by the fact that if we made this change then authors could
(to
On 2015/06/22 13:10, Shane Stephens wrote:
On Mon, Jun 1, 2015 at 2:39 PM Brian Birtles anim.play());
elem.getAnimations(); // returns a, b, c. What??
This is slightly odd, but quite explainable and definitely a corner case.
I'm concerned these little oddities tend to le
Dear all,
The editors of the Web Animations specification would like to publish
another Working Draft based on the current Editor's Draft.[1] A (rather
long) list of changes is included at the end of this mail.
We plan to publish on July 2 unless there are any objections.
Best regards,
Brian
lt of that discussion.
Best regards,
Brian
[1] https://github.com/w3c/web-animations/issues/62
Best,
- Kris
[1] http://w3c.github.io/web-animations/#dom-animatable-getanimations
[2] http://w3c.github.io/web-animations/#custom-animation-priority
On Sun, May 31, 2015 at 9:38 PM, Brian Birtles mailt
Hi,
I'm trying to nail down the ordering of animations so I can implement it
in Firefox. I wrote up an outline of this on Github[1] and went over it
with Shane, Doug and Mike last week who agreed it seems reasonable.[2]
Coming to implement this now, however, I've come across the following
ed
Web Animations minutes, 25 May 2015
Present: Doug, Mike, Shane, Brian
Archived etherpad:
https://web-animations.etherpad.mozilla.org/ep/pad/view/ro.92487irtSfEow/rev.37544
Agenda:
1. Name property
2. Can we drop AnimationTimeline.play?
3. AnimationTimeline.getAnimations() - sequencing
4. Use c
Web Animations minutes, 27 April 2015
Present: Doug, Shane, Brian
Archived etherpad:
https://web-animations.etherpad.mozilla.org/ep/pad/view/ro.92487irtSfEow/rev.33376
Agenda:
1. Property-indexed keyframes
2. Finishing behavior
3. Publishing next WD
4. Negative infinity start delay
5. Add / ac
Hi,
Thanks for looking into this!
On 2015/04/24 7:13, Shane Stephens wrote:
...
> This is a really good summary of the different states and how to
> transition between them. Could we insert this in the non-normative text
> of the spec?
Thanks. I filed issue #92 for this.[1]
> I thought abo
Hi,
If an animation is in the idle state and the current time is set, the
currently spec'ed behavior is that the animation will transition to the
running state.
This is because when the current time is set, none of the conditions
that would cause us to update the hold time are fulfilled.[1]
On 2015/04/17 14:34, Glen Huang wrote:
The difficulty for a JS implementation is to make sure the times reported by
the timeline etc. match up with the current frame even when the polyfill is not
listening for frames but something else is generating them
Yes, that's the difficulty I encounter
On 2015/04/14 16:39, Brian Birtles wrote:
...
e. Should 'paused' really win over 'finished'? The fundamental problem
here is that 'paused' and 'finished' are really orthogonal. It's
possible to be both at once. That said, I'm less than enthus
Hi Glen,
On 2015/04/15 15:37, Glen Huang wrote:
If I understand the spec correctly, in the case of keyframe effects, an UA is
expected to periodically update all keyframe effects.
I'm not sure exactly what you mean by updating keyframe effects. Are you
referring to the times returned by the
On 2015/04/15 13:58, Glen Huang wrote:
I think I understand it now.
What the reschedule step is really trying to do is to delay the pending task.
And it can be equivalently expressed as canceling the current pending task, and
then queue a new task doing what the original pending task was suppo
On 2015/04/11 15:48, Glen Huang wrote:
Hi Brian,
Thanks for the explanation.
The explanation is perfectly clear, but I'm unable to relate it to the
requirement "reschedule that task to run as soon as animation is ready".
This doesn't seem to have anything to do with delaying the resolving of
th
Hi,
We previously resolved[1] to add some extra methods to the Animation
interface. I've been going over this and I'm not sure how much we
actually need to change.
First, recall the states of an Animation which we can simplify to the
following three:
idle = no current time (*may* have a
On 2015/03/10 21:55, "Сергей Грехов" wrote:
Time fraction calculation algorithm
(http://w3c.github.io/web-animations/#calculating-the-time-fraction)
contains several steps for the case when iteration duration is zero. It's
not obvious to understand the idea of thes algorithm looking at algorithm
On 2015/03/06 19:19, Aleksei Semenov wrote:
Hello, everyone.
The specification defines two interfaces: AnimationReadonly and Animation.
First one is read-only, second is mutable.
https://w3c.github.io/web-animations/#the-animation-interfaces
The examples in the specification refer only to Anima
On 2015/03/06 15:54, "Сергей Грехов" wrote:
Hi All,
AnimationTiming interface definition is the following
(https://w3c.github.io/web-animations/#the-animationtiming-interface):
The AnimationTiming interface is a mutable subclass of
AnimationTimingReadonly returned for the timing attribute of a
On 2015/03/06 15:35, Aleksei Semenov wrote:
Hello, everyone.
The definition of the AnimationPlayer.currentTime attribute reads:
( https://w3c.github.io/web-animations/#dom-animationplayer-currenttime )
currentTime, of type double, nullable
The current time of this player unless this playerhas
On 2015/03/03 19:35, Aleksei Semenov wrote:
Hello, everyone.
It looks strange, that iteration composite operation
( https://w3c.github.io/web-animations/#iteration-composite-operation )
defines only two operations: replace and accumulate.
While there are three operations for animation compositio
On 2015/03/05 15:35, "Сергей Грехов" wrote:
Hi all,
Animatable.animate()
(http://w3c.github.io/web-animations/#the-animatable-interface) contains
the following examples:
EXAMPLE 15
var anim = elem.animate({ opacity: 0 }, 2000);
is equivalent to:
EXAMPLE 16
var anim = new Animation(elem, { opa
On 2015/02/25 17:07, Aleksei Semenov wrote:
Hello, everyone.
The specification reads
https://w3c.github.io/web-animations/#animation-node-start-time
The start time of an animation node is the moment in inherited
timewhen the animation node is scheduled to begin. In the absence of
animation gro
On 2015/03/02 20:30, Aleksei Semenov wrote:
Hello, everyone.
https://w3c.github.io/web-animations/#distribute-keyframe-spacing-mode
reads:
distribute
Indicates that keyframes with a null keyframe offset null are
positioned so that the difference between subsequent keyframe offsets
are equal.
Hi Sergey,
On 2015/03/02 14:45, "Сергей Грехов" wrote:
Please note that both fill mode definition (3.7.1. Fill modes,
http://w3c.github.io/web-animations/#fill-modes) is the following:
When the animation node backwards fill behavior is used.
When the animation node forwards fill beha
Hi Sergey,
Sorry for the delay in getting back to all this feedback. I'm working
through it bit by bit.
On 2015/02/25 15:35, "Сергей Грехов" wrote:
Please note that Example 13 in 5.9.2. Creating a new Animation object
(http://w3c.github.io/web-animations/#creating-a-new-animation-object)
stil
On 2015/03/12 10:54, Shane Stephens wrote:
On Thu, Mar 12, 2015 at 12:38 PM Brian Birtles Furthermore, keyframe lists should only deal with specified lists
- the
> problem you're describing doesn't need to exist as accessors on a
> KeyframeList should return the u
On 2015/03/12 13:15, Glen Huang wrote:
```js
elem.style.opacity = 1;
let anim = elem.animate({ opacity: 0 }, { duration: 500, fill: "forwards"});
anim.ready.then(() => {
anim.effect.timing.fill = "none";
console.log(elem.style.opacity);
});
```
Is that supposed to be anim.finish
On 2015/03/12 13:02, Glen Huang wrote:
In the section 5.19 of the branch, it says "if the Animation associated with an
Animation is seeked”, should it be "if the Animation associated with a
KeyframeEffect is seeked”?
Yes, I expect there will be a few new bugs like that (I probably touched
mo
On 2015/03/12 10:10, Shane Stephens wrote:
Unfortunately I was unable to make a shared keyframe list since as was
discussed at one stage.[3] This is because keyframe lists return their
computed offsets but for paced keyframe lists, the computed offset may
depend on their target e
Hi,
Back in February I proposed a possible simplification to the Web
Animations API.[1] If you haven't had a look, please do, but as an
overview it looks something like:
* Merge Animation and KeyframeEffect and call it KeyframeEffect
* Rename AnimationPlayer to Animation
There was no opposit
Hi Aleksei,
On 2015/02/19 21:31, Aleksei Semenov wrote:
...
As you can see, the definition of animation node does not define any
additional
properties, that can be used to distinguish animation nodes from other
timing nodes.
Furthermore, the role (or function) of animation node is also not defin
Hi Sergey,
On 2015/02/19 20:17, "Сергей Грехов" wrote:
Hi All,
Please see the second non-normative section, containing Example 19, in
5.21. Script execution and live updates to the model
(https://w3c.github.io/web-animations/#script-execution-and-live-updates-to-the-model).
That whole section
Hi Aleksei,
Thanks for your mail.
On 2015/02/18 18:48, Aleksei Semenov wrote:
Hello, everyone.
The section '3.5.11. Reaching the end' describes the player behavior,
when it reaches its boundaries (either start or finish).
The section also contains a picture to demonstrate the effect of limitin
Hi Sergey,
Thanks for the feedback. Comments below.
On 2015/02/17 22:28, "Сергей Грехов" wrote:
1) WebIDL for KeyframeEffect
(http://w3c.github.io/web-animations/#the-keyframeeffect-interfaces)
contains the following
// Mutable additions to KeyframeEffectReadonly interface
inherit at
Hi Glen,
On 2015/02/12 21:49, Glen Huang wrote:
You examples make me read the spec again, and if I’m not wrong, the timing
functions specified in each keyframe and in the animation node are
*accumulative* (keyframes apply the specified time function to the time
fractions they receive from the
Web Animations minutes, 14 Feb 2015
Present: Doug, Shane, Brian
Archived etherpad:
https://web-animations.etherpad.mozilla.org/ep/pad/view/ro.92487irtSfEow/rev.32354
Agenda:
1. What is the set of animations returned from getAnimationPlayers()?
2. play(), pause etc. and returning Promises
3. Re
On 2014/12/11 19:18, Aleksei Semenov wrote:
Hi, everyone.
Please, consider the following example:
var keyframes = [
{top: '10%'},
{top: '20%'},
{top: '50%'}
];
var effect = new KeyframeEffect(keyframes, 'paced(top)');
effect.getFrames(
On 2015/02/10 17:33, "Сергей Грехов" wrote:
Non-normative section of 3.9. Core animation node calculations
(http://w3c.github.io/web-animations/#core-animation-node-calculations)
still contains playback rate (see picture illustrated scaled active time)
which was removed from the current level of
On 2015/02/10 18:03, Aleksei Semenov wrote:
The procedure to pause a player reads (
http://w3c.github.io/web-animations/#pause-a-player ):
...
6. Schedule a task to be executed at the first possible momentafter
the user agent has performed any processing necessaryto suspend the
playback of playe
On 2015/02/10 18:47, Glen Huang wrote:
Both css transition and css animations use “ease” as the default timing
function. Why web-animations use “linear” instead?
Hi Glen,
Thanks for your mail. I like the idea of aligning better with CSS
however there is a slight difference in the way Web An
Web Animations minutes, 10 Feb 2015
Present: Doug, Shane, Brian
Archived etherpad:
https://web-animations.etherpad.mozilla.org/ep/pad/view/ro.92487irtSfEow/rev.30455
Agenda:
1. Renaming and simplification
2. Reworking current / in play / relationship between nodes and players
3. Renaming to it
Hi Aleksei,
Thanks for your mail.
Firstly, I think there may be a couple of points of confusion in the
second part.
On 2015/01/23 22:02, Aleksei Semenov wrote:
Another option:
player.pause(); // => let's assume that player is immediately ready,
// so pending pause task is not scheduled, all
On 2015/02/03 17:07, "Сергей Грехов" wrote:
Hi all,
It is said in the specification
(http://w3c.github.io/web-animations/#typedef-cubic-bezier-timing-function)
cubic-bezier(, , , )
Specifies a cubic Bézier timing function. The four numbers specify
points P1 and P2 of the curve as (x1, y1,
On 2015/01/18 8:22, Miguel Camba wrote:
Just to put everyone in context, the motivation of this email came from
this GH issue in web-animations-next polyfill.
https://github.com/web-animations/web-animations-next/issues/270
Hi Miguel,
Thanks for reporting this. I think it makes sense to expos
On 2015/02/09 17:53, "Сергей Грехов" wrote:
Hi All,
Animatable.getAnimationPlayers() definition
(http://w3c.github.io/web-animations/#dom-animatable-getanimationplayers)
contains the following statement. "If this object is the animation target
of two or more animations which are associated with
Hi,
There are a number of areas in the API I'm not comfortable with. In
particular:
* getAnimationPlayers() is odd. When you want to get the animations
running on an element, it would be much more natural to call
elem.getAnimations().
* Recent discussion about renaming AnimationPlayer.sour
Dear all,
In the interests of iterating more quickly, the editors of the Web
Animations specification decided to defer the animation group and
animation sequence features from Web Animations to the next level of the
specification.[1]
We believe these grouping primitives are still very powerf
Hi Aleksei,
On 2015/01/16 20:16, Aleksei Semenov wrote:
The Web Animations specification
http://w3c.github.io/web-animations/#the-current-ready-promise
reads:
Each player has a current ready promise.The current ready promise is
initiallya resolved Promise created using theprocedure to create a
On 2014/12/15 16:00, Сергей Грехов wrote:
Hi All,
It's unclear from the spec what values should return
computedTiming.iterationStart and fill attributes for some values.
This should be fixed in:
https://github.com/w3c/web-animations/commit/5d43856e957bffd9dc1ec28b286197d9ac8ec3d9
Thanks.
Ex
On 2014/12/17 15:09, "Сергей Грехов" wrote:
Hi All,
Format of scaled active time definition section is wrong. Seems there
should be "... + start_offset". Please see attached image.
Fixed in:
https://github.com/w3c/web-animations/commit/545af4361215de519460f46c7a46fa94ed2da9f6
Thanks.
On 2014/12/22 15:04, "Сергей Грехов" wrote:
Hi Tab,
Let's see note at
http://w3c.github.io/web-animations/#dom-animationtiming-iterationstart
"Note that the value of iterations is effectively added to the
iterationStart such that an animation node with an iterationStart of ‘0.5’
and iterations
On 2014/12/19 15:14, "Сергей Грехов" wrote:
player.ready.then(function() {
// Total duration of the sequence is 1000. Because of iteration
// start animation should begin from moment that corresponds
// time 100. animation1 is finished at this time.
// Wha
Web Animations minutes, 18 Dec 2014
Present: Doug, Shane, Brian
Archived etherpad:
https://web-animations.etherpad.mozilla.org/ep/pad/view/ro.92487irtSfEow/rev.28977
Agenda:
1. Should we call it timingFunction instead of easing?
2. How are the CSS integration specs coming along?
3. Setting the
Hi Aleksei,
Thanks for your question.
On 2014/12/03 19:38, Aleksei Semenov wrote:
According to the specification,
http://w3c.github.io/web-animations/#dom-keyframeeffect-getframes
spacing keyframes, i.e. attributes computedOffset are calculated in
method KeyframeEffect.getFrames().
Yes, but t
Web Animations minutes, 27 Nov 2014
Present: Doug, Dirk, Shane, Brian
Archived etherpad:
https://web-animations.etherpad.mozilla.org/ep/pad/view/ro.92487irtSfEow/rev.28425
Agenda:
1. If you set the startTime on a paused player, what happens?
2. Should the player states be pause-pending and pla
On 2014/11/26 14:57, "Сергей Грехов" wrote:
Hi All,
Example 6, Example 7 and Figures 28 and 29 in non-normative section of
4.3.1. Spacing keyframes
(http://w3c.github.io/web-animations/#spacing-keyframes) still use "paced"
spacing mode without paced property specified. According the latest
chang
Hi Aleksei,
On 2014/11/07 20:14, Aleksei Semenov wrote:
The default value for 'composite' attribute is specified as null (
http://w3c.github.io/web-animations/#dictdef-keyframe )
However if keyframe input contains attribute 'composite' with the value
null, the procedure for converting an ECMAScr
On 2014/11/14 2:08, Amelia Bellamy-Royds wrote:
...
In summary, if the above resolutions are adopted, there will be four
different error situations for filters:
1. If there is a syntax error or unsupported value in a CSS shorthand
filter function, the filter property declaration will be inv
On 2014/11/06 19:38, "Сергей Грехов" wrote:
Inverts the playback rate of this player and seeks to the start of the
source content if if has finished playing in the reversed direction using
the reverse a player procedure for this object
First, please note "...IF IF has finished...".
Second, the w
On 2014/11/06 15:00, "Сергей Грехов" wrote:
Hi Brian,
AnimationTimeline.play() method definition
(http://w3c.github.io/web-animations/#dom-animationtimeline-play) still
uses parameter of type TimedItem.
Fixed:
https://github.com/w3c/web-animations/commit/81e5196f691a41fded9bb528b28ba6eec24e7c
On 2014/11/05 16:25, Brian Birtles wrote:
Yes, this is clearly wrong. It came about because we've changed the
behaviour regarding if/when start time becomes unresolved a few times.
When the pause completes we should set the hold time to the result of
calculating the current time usin
On 2014/11/05 17:36, Sergey G. Grekhov wrote:
Missed that there's also step 7.4. Run the procedure to update a player's
finished state for player.
At least one of these steps (7.4 and 8) should be removed. Or maybe even
both of them.
Why is that? They are both necessary (to ensure, for example
On 2014/11/05 15:42, Sergey G. Grekhov wrote:
Hi All,
The procedure to pause a player
(http://w3c.github.io/web-animations/#pause-a-player) contains the
following steps:
…
4. Set player’s hold time to current time.
…
7.1. Set player’s hold time to the time value corresponding to the value
of
99 matches
Mail list logo