Re: Extend fullscreen API to support second screen

• From: Rottsches, Dominik <dominik.rottsches@intel.com>
• Date: Thu, 28 Aug 2014 14:23:43 +0000
• To: (wrong string) 垚 <duanyao@ustc.edu>
• Message-ID: <6293B092-CA85-47BB-A0A7-38D2FA2014E3@intel.com>

Hi Duan,

> What did the "hooking it into Fullscreen API" approach look like in your
> mind? and what requirements and use cases it couldn't match?

The requestFullscreen() function does not allow a screen choice for example. Also, just the naming does not match what we want to do. requestFullscreen() is a feature of a DOMElement. There are additional issues with “ripping out” a DOM element out of the one page, and placing it onto a remote screen. This would not work well in a two-UA implementation situation. So, starting with a new API seems like the better approach.

> Do you think we still want a Fullscreen API like, partial mirroring API,
> accompanied with the current Presentation API? App-level mirroring seems
> still hard with current Presentation API, and some demos require
> browsers' private APIs.

If your content is downloaded from a web server, I think “partial mirroring”, or showing the same content on two screens, nicely adapted to each screen's size and display resolution is not hard with Presentation API at it’s current incarnation. So personally I don’t think mirroring support in the API is a high priority.

Dominik

Received on Thursday, 28 August 2014 14:24:18 UTC