- From: Ingar Arntzen via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Jun 2018 12:41:51 +0000
- To: public-web-and-tv@w3.org
@Snarkdoof - as you indicate, if *timeUpdate* events were timestamped by the media player (using a common clock - say performance.now), then it would become much easier to maintain a precise, interpolated media clock in JS. Importantly, the precision of such an interpolated clock would not be highly sensitive to the frequency of the *timeUpdate* event (so we could avoid turning that up unnecessarily). In addition, a precise interpolated media clock is a good basis for using timeouts to fire *enter/exit* events for subtitles etc. If one would prefer enter/exit events to be generated natively within the media element, using timeouts instead of poll-based *time-marches-on* should be an attractive solution there as well. So, adding timestamps to media events seems to me like a simple yet important step forward. Similarly, there should be timestamps associated with control events such as play, pause, seekTo, ... -- GitHub Notification of comment by ingararntzen Please view or discuss this issue at https://github.com/w3c/media-and-entertainment/issues/4#issuecomment-397608365 using your GitHub account
Received on Friday, 15 June 2018 12:41:54 UTC