- From: Philip Jägenstedt via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Jun 2016 08:22:38 +0000
- To: public-secondscreen@w3.org
So let's just list all of the things that one can do: * Set `src`, call `load()` or otherwise cause the current resource to be abandoned * Seek (fast or accurate, `fastSeek` is implemented in WebKit) * Pause/play * Change playback rate * Change volume and mute * Change enabled audio/video tracks * Change enabled text tracks Which of these might be problematic on the remote side? Do we expect to have implementations where the volume can't be changed at all? Where changing the enabled audio track doesn't work? The most troubling of these to me is actually text tracks. WebVTT is built on other web technologies, and if the remote isn't also a web engine, then it would have to be an independent implementation of WebVTT, and it's somewhat likely that just won't be done. @zcorpan -- GitHub Notification of comment by foolip Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/41#issuecomment-222925224 using your GitHub account
Received on Wednesday, 1 June 2016 08:22:40 UTC