- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Wed, 13 Aug 2014 14:49:13 +0000
- To: "public-webscreens@w3.org" <public-webscreens@w3.org>
- CC: Francois Daoust <fd@w3.org>
On 17 Jun 2014, at 16:48, Kostiainen, Anssi <anssi.kostiainen@intel.com> wrote: > In the spirit of experimentation I wrote a Presentation API prollyfill (= a polyfill for a not yet standardized API) for the HTMLMediaElement to get a feel of the API ergonomics. Thanks to the first contribution to the requestShowMedia.js project (Thanks Francois!), rSM.js now supports Chromecast devices too. In a nutshell, this prollyfill implemented atop the Presentation API plumbings allows you to cast any HTML5 <video> element to your Chromecast device by means of just calling requestShow() on the video element to be casted. The standard HTMLMediaElement methods play(), pause(), and fastSeek(time) on the video element are used to control the playback on the second screen. To demonstrate another implementation approach, the video is displayed on a second screen that is attached to your system using HDMI, VGA, or wirelessly using Miracast or WiDi if you’re using our experimental Chromium build (see the demo page for details). Lastly, there’s a fallback that works in all modern browsers that emulates a second screen using a new browser window. Here’s the demo: http://webscreens.github.io/requestshowmedia/demo/ And here’s how a web developer might use the prollyfill: https://github.com/webscreens/requestshowmedia#how-it-works All feedback is welcome. I hope that these continued experiments provide helpful feedback in our journey to evolve the API. Thanks, -Anssi
Received on Wednesday, 13 August 2014 14:51:27 UTC