Re: [css-transitions]: Lacking satisfying specification interrupted transitions

In regard to http://dev.w3.org/csswg/css-transitions/#reversing:


There it reads “Note that these rules do not fully address the problem for 
transition patterns that involve more than two states.”

Actually, there is no need to consider any previous state on interrupted 
transitions.

We won’t be able to time travel in the foreseeable future, so we will never 
return to any previous state but only move forward.


Here’s an example of blending two pictures:

Transition #1 blends from image [a] to image [b]. Transition #2 blends to 
image [c].


When we are interrupting transition #1 somewhere in the middle, the 
resulting image shows a blended version of [a] –> [b]. Let’s call it [ab].

Given my suggested algorithm, [ab] will be the starting image for transition 
#2. So there is no need to store any previous states ([a] or [b] in this 
case). We just take a snapshot of the current situation ([ab]) and take it 
as the start value for transition #2, shortening its absolute running time 
accordingly.

tl;dr : At the time of interruption neither [a] or [b] exist anymore as a 
computed value. So there will never be more than two states.


Axel Dahmen

Received on Friday, 20 March 2015 10:54:25 UTC