- From: Nigel Megitt via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Jun 2018 13:44:17 +0000
- To: public-web-and-tv@w3.org
Thanks @tidoust that is helpful. Last time I looked at this, a month or so back, I assured myself that _time marches on_ itself could be run only every 250ms conformantly, but the spec text you pointed to suggests that timing constraint only applies to `timeupdate` events. Now I wonder if I misread it originally. Nevertheless, time marches on frequency is dependent on some unspecified observation of the current playback position of the media element changing, which looks like it should be more often than 4Hz (every frame? every audio sample?). In practice, I don't think browsers _actually_ run time marches on whenever the current playback position advances by e.g. 1 frame or 1 audio sample. The real world behaviour seems to match the timing requirements for firing `timeupdate` events, at the less frequent end. -- GitHub Notification of comment by nigelmegitt Please view or discuss this issue at https://github.com/w3c/media-and-entertainment/issues/4#issuecomment-398058632 using your GitHub account
Received on Monday, 18 June 2018 13:44:24 UTC