W3C home > Mailing lists > Public > public-secondscreen@w3.org > March 2015

Re: [presentation-api] Presenting the content of an <audio> or <video> element

From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
Date: Wed, 18 Mar 2015 08:47:37 +0000
To: public-secondscreen@w3.org
Message-ID: <issue_comment.created-82823859-1426668456-sysbot+gh@w3.org>
> Might a similar thing happen here, so that a 
Element.requestRemotePresentation() or something would be appropriate?
 Or possibly it could be integrated with the Fullscreen API with extra
 arguments to Element.requestFullscreen()? (Sorry if this is 
nonsensical, I'm not really up to speed with the Presentation API.)

We discussed this at some point, but there are some tricky issues with
 extracting arbitrary elements from the DOM, then moving individual 
block-displayed elements and stretching them to the remote screen's 
aspect ratio etc. What happens to media queries, what happens to 
associated resources from the original DOM - how do they get 
transfered to the remote screen? This is hard to implement in a 
two-user-agents scenario, etc. - that's why we went for passing only a
 "presentation URL" to the presentation display and using that. So I 
wouldn't expect an ```Element..requestRemotePresentation()``` for 
elements generically, but for video elements I think this may work.

GitHub Notif of comment by drott
Received on Wednesday, 18 March 2015 08:47:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:18:51 UTC