Skip to content
This repository was archived by the owner on Jun 7, 2018. It is now read-only.

Overflow fill #22

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Overflow fill #22

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ac3c1c6
Fix current iteration when iteration duration is zero
steveblock Dec 17, 2013
48a7256
Overflow fill
steveblock Dec 17, 2013
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
141 changes: 93 additions & 48 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1207,6 +1207,29 @@ <h3>Local time and inherited time</h3>
If the <a>inherited time</a> is <code>null</code> then the local time
is also <code>null</code>.
</p>
<p>
For a <a>timed item</a>, the <dfn>inherited overflow boundary</dfn> at
a given moment is based on the first matching condition from the
following:
</p>
<dl class="switch">
<dt>If the <a>timed item</a> has a <a>parent timing group</a>,</dt>
<dd>
the inherited overflow boundary is the <a>parent timing
group</a>'s <a>overflow boundary</a>.
</dd>
<dt>Otherwise,</dt>
<dd>
the inherited overflow boundary is <code>null</code>.
</dd>
</dl>
<p>
The <dfn>parent overflow boundary</dfn> of a <a>timed item</a> is
the <a>timed item</a>'s <a>inherited overflow boundary</a> minus its
<a title="timed item start time">start time</a>.
If the <a>inherited overflow boundary</a> is <code>null</code> then
the parent overflow boundary is also <code>null</code>.
</p>
</section>
<section>
<h3>Timed item phases and states</h3>
Expand Down Expand Up @@ -1267,7 +1290,8 @@ <h3>Timed item phases and states</h3>
Corresponds to a <a>timed item</a> whose <a>active time</a> is
changing on each sample.
This occurs when the <a>timed item</a> <em>and all its
ancestors</em> are in the <a>active phase</a>.
ancestors</em> are <a>in play</a> and the root ancestor is in
the <a>active phase</a>.
<a>Animations</a> only &ldquo;move&rdquo; when they are
<a>in play</a>.
</p>
Expand All @@ -1281,6 +1305,17 @@ <h3>Timed item phases and states</h3>
snapshotted within the <a>active phase</a> despite no longer
being <a>in play</a>.
</p>
<p>
Conversely, it is possible for a <a>timed item</a> to be <a>in
play</a> without being in the <a>active phase</a>.
For example, a <a>parent timing group</a> that is <a>in
play</a> may have a <a>timing function</a> which causes it to
be <a>overflowing</a>.
The child <a>timed item</a> of such a <a>parent timing
group</a> may be in <a>in play</a> even if its local time
falls outside its <a>active interval</a>, causing it to not be
in the <a>active phase</a>.
</p>
<p>
Transitions to and from the <a>in play</a> state trigger
timing events as defined in <a href="#timing-events"
Expand Down Expand Up @@ -1356,18 +1391,19 @@ <h3>Timed item phases and states</h3>
duration</a>.
</p>
<p>
A <a>timed item</a> is <dfn>in play</dfn> if <em>all</em>
A <a>timed item</a> is <dfn>in play</dfn> if <em>any</em>
of the following conditions are met:
</p>
<ol>
<li>the <a>timed item</a> is in the <a>active phase</a>, and
<li>the <a>timed item</a> has a <a>parent timing group</a> that is
<a>in play</a> or else is <a>directly associated with a player</a>
that is not <a>bounded</a>.
</ol>
<ul>
<li>the <a>timed item</a> is in the <a>active phase</a> and has a
<a>parent timing group</a> that is <a>in play</a> or else is
<a>directly associated with a player</a> that is not
<a>bounded</a>.
<li>the <a>timed item</a> is <a>overflowing</a>.
</ul>
<p>
A timed item is <dfn>current</dfn> if it <em>any</em> of the following
conditions is true:
conditions are true:
</p>
<ul>
<li>it is in the <a>before phase</a>, or
Expand All @@ -1381,6 +1417,15 @@ <h3>Timed item phases and states</h3>
href="#calculating-the-active-time" class="sectionRef"></a> is not
<code>null</code>.
</p>
<p>
A timed item is <dfn>overflowing</dfn> if its <a>parent overflow
boundary</a> is not <code>null</code> and falls inside its <a>active
interval</a>.
</p>
<div class="note">
Note that this definition of overflow means that the property is not
inherited. It is possible for a timed item to not overflow even
though its parent is overflowing.
</section>
</section>

Expand Down Expand Up @@ -1475,26 +1520,6 @@ <h3>Fill modes</h3>
item is only defined (that is, not <code>null</code>) inside the
<a>active interval</a> <em>or</em> when a fill is applied.
</p>
<div class="issue">
<p>
Currently <a>timing functions</a> that generate results outside the
range [0, 1] will behave unexpectedly when applied to animation
groups, as children will increase iterations or enter into fill mode
rather than continuing to extrapolate along their defined behavior
(which is what they would do if the timing function applied to them
directly).
</p>
<p>
To fix this it is possible we will wish to introduce 'overflow' fill
modes that respond to time values larger than or smaller than the
active time range by extrapolating rather than filling.
</p>
<p>
See <a
href='http://lists.w3.org/Archives/Public/public-fx/2013AprJun/0184.html'>section
15 (Overflowing fill) of minuted discussion from Tokyo 2013 F2F</a>.
</p>
</div>
</section>
</section>

Expand Down Expand Up @@ -1909,11 +1934,17 @@ <h4>Calculating the active time</h4>
The <dfn>active time</dfn> is based on the <a>local time</a>
and <a>start delay</a>.
However, it is only defined when the <a>timed item</a> should
produce an output and hence depends on its <a>fill mode</a> and
phase as well as the phase of its <a>parent timing group</a>, if
any, as follows,
produce an output and hence depends on its <a>fill mode</a>, phase
and whether it is <a>overflowing</a>, as well as the phase of its
<a>parent timing group</a>.
It is calculated using the first matching condition from the
following,
</p>
<dl class="switch">
<dt>If the timed item is <a>overflowing</a>,</dt>
<dd>
Return <code><a>local time</a> - <a>start delay</a></code>.
</dd>
<dt>If the timed item is in the <a>before phase</a>,</dt>
<dd>
The result depends on the <a>fill mode</a> as follows.
Expand Down Expand Up @@ -2048,16 +2079,17 @@ <h4>Calculating the iteration time</h4>
If the <a>iteration duration</a> is zero, return zero.
</li>
<li>
If <code><a>scaled active time</a> - <a>start
offset</a></code> is equal to the <a>repeated duration</a>,
and <a>iteration count</a> is not zero,
and <code>(<a>iteration count</a> + <a>iteration start</a>)
% 1</code> is zero,
return the <a>iteration duration</a>.
If the <a>current iteration</a> is zero, return <a>scaled active
time</a>.
<p class="note">
This clarification is needed since the <a>iteration duration</a>
may be infinity and the result of infinity multiplied by zero is
undefined according to IEEE 754-2008.
</p>
</li>
<li>
Otherwise, return <code><a>scaled active time</a>
% <a>iteration duration</a></code>.
Otherwise, return <code><a>scaled active time</a> - <a>current
iteration</a> &times <a>iteration duration</a></code>.
</li>
</ol>
</section>
Expand All @@ -2078,16 +2110,14 @@ <h3>Calculating the current iteration</h3>
</li>
<li>
If the <a>iteration duration</a> is zero, return
<code>floor(<a>iteration start</a> + <a>iteration count</a>)</code>.
<code>ceil(<a>iteration start</a> + <a>iteration count</a>) -
1</code>.
</li>
<li>
If the <a>iteration time</a> equals the <a>iteration
duration</a>, return <code><a>iteration start</a>
+ <a>iteration count</a> - 1</code>.
</li>
<li>
Return <code>floor(<a>scaled active time</a> /
<a>iteration duration</a>)</code>.
Return the result of evaluating <code>floor(<a>scaled active
time</a> / <a>iteration duration</a>)</code>, clamped to the range
<code>[0, ceil(<a>iteration start</a> + <a>iteration count</a>) -
1]</code>.
<p class="note">
If the <a>iteration duration</a> is infinite, the
result of <code>floor(<a>scaled active time</a> /
Expand Down Expand Up @@ -3095,6 +3125,21 @@ <h3>Calculating the transformed time</h3>
</p>
</ol>
</section>
<section>
<h3>Calculating the overflow boundary</h3>
<p>
The <dfn>overflow boundary</dfn> is calculated from the
<a>transformed time</a> using the following steps:
</p>
<ol>
<li>If the <a>transformed time</a> is <code>null</code>, return
<code>null</code>.
<li>If the <a>transformed time</a> is less than zero, return zero.
<li>If the <a>transformed time</a> is greater than or equal to the
<a>iteration duration</a>, return the <a>iteration duration</a>.
<li>Otherwise, return <code>null</code>.
</ol>
</section>
</section>

<section>
Expand Down