Will merge back once it's more-or-less internally consistent
* Made a flipclock demo - will upload it to github soon
* nothing relevant to WebAnim (sorry!)
* polyfill refactoring to meet new API
2. COMPOSITING ORDER AND START TIMES
How do we order the animations for compositing within a tree when there is only one (specified) start time now (on the Player)?
Suggest ordering is firstly, by (player) start time, then within a tree it is depth-first tree order.
How does this work for repetition? It no longer affects the order. It used to when we ordered by "actual start time" (i.e. the calculated time when a given interval begins)
Steve to make change to polyfill
3. START TIME DEFAULTS
Current behavior of polyfill (and presumably spec at some time in past) is that the default start time of a TimedItem in a ParGroup is the parent's iteration time. (Children of SeqGroups always have a forced start time).
In the Player model, start time won't be exposed, and will be calculated by the model and not settable. We should make the calculated start time zero for children of ParGroups. (Note that before attaching to a Player, the parent's iteration time is always zero, so there's no change in behaviour before attachment, only after attachment).
All in agreement.
Steve will update polyfill.
4. Element.animate RETURNING Animation
Doug: An argument for this choice - it's useful for building animation trees. eg.