Platform/Layout/Web Animations: Difference between revisions

Platform/Layout/Web Animations (view source)

1,336 bytes added , 21 May 2013

Add minutes for 2013-05-21

Confirmed users

166

edits

@@ Line 217: / Line 217: @@
 I'm not sure how much all this matters?
+== Minutes from 2013-05-21 ==
+* Some concern expressed over complexity of model
+** In particular, the Player concept seems confusing. Possible preference for play/pause directly on animate? Or removing the timeline?
+** Possible interest in identifying a subset for implementation
+* Some issues identified:
+** Need extra hooks into the prioritization of animations to control where, for example, transitions apply
+** Need means to start animations before document load (CSS Transitions/Animations do this despite wording in early drafts)
+** Need to define what happens when a player refers to the document timeline of one document but its animations refer to elements in another document
+** Not sure if <code>Player.startTime</code> needs to be writeable
+* Brief discussion of listed issues suggests:
+** Issue 2: Some concern over the numbers using in proposed timing function list syntax.
+** Issue 3: <code>play()</code>/<code>playNow()</code> ''may'' be ok. Use of Futures seems a bit weird.
+** Issue 5: KeyframeShortcut only is probably fine.
+Follow-up meeting: Thurs 2pm Taipei time (0600 UTC)
+Agenda for next meeting:
+* If we were to implement it, how could we approach it?
+** Is there a subset we could focus on? Can we implement without the API? etc. etc.
+* Re-visiting the issues listed above that we haven't yet discussed
 == Implementation ==