- From: Marcos Caceres <mcaceres@mozilla.com>
- Date: Thu, 11 Sep 2014 15:43:57 -0400
- To: public-web-perf@w3.org
- Cc: Mounir Lamouri <mlamouri@google.com>
*** THIS IS IMPLEMENTER FEEDBACK - PLEASE DON'T IGNORE IT *** The spec uses the concept of "queue a task" but fails to define a task source. Task queues depend on task sources and hence one MUST be explicitly defined or mentioned in the spec. APIs, such as the Screen Orientation API rely on the interaction between when the page visibility values are changed and the event is fired - but because there is no task source, it's not possible to wire them up together using prose :( See: https://github.com/mounirlamouri/screen-orientation/commit/b9737dabcae6fa994f3402162d0db3c76af2492b I don't know exactly which one to use, maybe the "animation frame task source" - see: http://lists.w3.org/Archives/Public/www-dom/2014JulSep/0061.html I imagine there is some interplay between page visibility and requestAnimationFrame(). PS: When are the specs of this group going to move to GitHub? I thought there was agreement for that to happen?
Received on Thursday, 11 September 2014 19:44:30 UTC