- From: Google <sysbot+gh@w3.org>
- Date: Tue, 29 May 2018 20:45:50 +0000
- To: public-secondscreen@w3.org
mfoltzgoogle has just created a new issue for https://github.com/w3c/remote-playback: == Explore polyfilling Remote Playback API on top of Presenation API == >From https://www.w3.org/2018/05/17-webscreens-minutes.html#x03: Chrome is [moving its current implementation](https://bugs.chromium.org/p/chromium/issues/detail?id=517102) of the Remote Playback API to be based on its implementation of the Presentation API. This suggests that it may be possible to polyfill the Remote Playback API on top of the Presentation API. There would be a number of issues with this approach that could lead to a poor user experience however. - Only reasonable to support `src=` media sources (polyfilling MSE to support remote playback seems quite difficult). - Difficult to match media container/codec with media capabilities of the display for accurate screen availability. - Lack of integration with default media controls. - Inability to determine CORS compatibility or forward cookies for remote playback. At any rate, this issue is tracking this idea for posterity, in case someone wants to do some prototyping in this area. Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/119 using your GitHub account
Received on Tuesday, 29 May 2018 20:45:56 UTC