- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Sat, 16 Feb 2019 15:18:55 +0000
- To: public-web-and-tv@w3.org
Step 6 is normative but I think we're reading the step differently. Where does it say that `timeupdate` is to happen after at most 250ms? I read the step as asking the user agent to choose a time between 15 and 250ms and to check, when this step is run, whether more than this value has elapsed since last time such an event was fired. The value selected by the user agent (e.g. 250ms) is a lower bound of a desired interval, not an upper bound. In any case, what I'm proposing is actually not to read too much into implicit assumptions and requirements, not to mention `timeupdate` events when it's not needed, and to point out that HTML does not set the rate at which the time marches on steps need to run explicitly at a value that would allow frame accuracy. -- GitHub Notification of comment by tidoust Please view or discuss this issue at https://github.com/w3c/me-media-timed-events/pull/35#issuecomment-464354967 using your GitHub account
Received on Saturday, 16 February 2019 15:18:57 UTC