- From: Francois Daoust <fd@w3.org>
- Date: Mon, 08 Jun 2015 17:35:03 +0200
- To: public-webtiming@w3.org
Continuing to think out loud here, What is the purpose of the "timeupdate" events as currently defined? http://webtiming.github.io/timingobject/#events More specifically: 1. Is the expectation that "timeupdate" events get fired synchronously across devices, or that they are associated with the "position" of the timing object? The spec does not suggest that and I did not do that in my prototype implementation, but then it seems a bit useless if it is only a shorthand to the local setInterval function. 2. Why a 5hz fixed frequency? Is it a common frequency for most media-related operations? Not having any sort of flexibility seems weird. I guess I see value in having something synchronized across devices and a bit more flexible, synchronized versions of "setTimeout" and "setInterval" in short that could be exposed on a TimingObject instance. I see that it is in fourth position in the list of tasks for the group, so that's good ;) https://www.w3.org/community/webtiming/overview/ Francois.
Received on Monday, 8 June 2015 15:35:12 UTC