- From: Rob Smith via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Nov 2018 17:27:14 +0000
- To: public-web-and-tv@w3.org
[WebVMT](http://w3c.github.io/sdw/proposals/geotagging/webvmt/) displays output in a separate HTML element, rather than within the media container, so latency is not particularly noticeable as the media and map displays are not generally overlaid. It uses a keyframe approach for animation, so again latency is not particularly noticeable. A worst case scenario would be a media scene change which instantly moves to a different location and requires the map to 'jump' concurrently. However, there are other inherent delays, such as loading times for the new map tiles, that would be needed at the same time in this case, so it is only one of many factors. The [HTML5 Embedded Content](https://www.w3.org/TR/html52/semantics-embedded-content.html) document currently cites 250ms as the maximum response time for events. -- GitHub Notification of comment by rjksmith Please view or discuss this issue at https://github.com/w3c/me-media-timed-events/issues/22#issuecomment-439466379 using your GitHub account
Received on Friday, 16 November 2018 17:27:15 UTC