- From: Brian Birtles <bbirtles@mozilla.com>
- Date: Fri, 22 Feb 2013 08:45:28 +0900
- To: "public-fx@w3.org" <public-fx@w3.org>
Web animations minutes, 21 / 22 February 2013 Etherpad: https://etherpad.mozilla.org/ep/pad/view/ro.Dq29jMyo7HW/latest Present: Doug, Shane, Steve, Brian Agenda: 1. Status update 2. Compositing order and start times 3. Start time defaults 4. Element.animation returning Animation 1. STATUS UPDATE ================ Brian: * Started making changes from F2F. Currently working on a separate branch: https://dvcs.w3.org/hg/FXTF/raw-file/separate-api/web-anim/index.html Will merge back once it's more-or-less internally consistent Doug: * Made a flipclock demo - will upload it to github soon Shane: * nothing relevant to WebAnim (sorry!) Steve: * 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. new ParGroup([ thing1.animate(...), thing2.animate(...)]); Brian: Also: element.animate({ 'opacity': '0%'}, 2).onend = function(e) { e.target.parentNode.removeChild(e.target); }; Next meeting: Thurs Feb 28 15:00 PST / Fri 1 Mar 10:00 AEDST / Fri 1 Mar 08:00 JST @ https://etherpad.mozilla.org/dzST4lrQ1t provided we have something to discuss Past meetings: http://www.w3.org/Graphics/fx/wiki/Web_Animations/Meetings
Received on Thursday, 21 February 2013 23:45:56 UTC