- From: Ingar Mæhlum Arntzen <ingar.arntzen@gmail.com>
- Date: Thu, 6 Aug 2015 14:30:16 +0200
- To: public-webtiming@w3.org
- Message-ID: <CAOFBLLqijMNYgdxJOFKqD1JEJd-yUFX5WX_CwfQW8+_vfFWZsQ@mail.gmail.com>
Hi all. I have gone through section 9 describing how media elements may be extended with support for timing objects as an external timing source. http://webtiming.github.io/timingobject/#media-elements-and-timing-objects Changes include: - added introduction with explanatory text, defining "default playback mode" and "timed playback mode" for media elements - minor changes to existing text/procudures - changed spec so that .currentTime of media element directed by timing object reports currentTime of internal media player, instead of position of the timing object. Would there any objections to this? The spec currently states that setting .currentTime on the mediaelement should be prohibited. This is the case for MediaControllers. An attractive (in my view) alternative would be to map setting of currentTime onto a request to the timing object. Following this approach, other media control commands such as play and pause could be mapped similarly. Would it be problematic to be inconsistent with the MediaController on this issue.? Ingar
Received on Thursday, 6 August 2015 12:30:45 UTC