- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Wed, 8 Jan 2014 14:29:35 +0000
- To: "Bassbouss, Louay" <louay.bassbouss@fokus.fraunhofer.de>
- CC: Anton Vayvod <avayvod@google.com>, "public-webscreens@w3c.org" <public-webscreens@w3c.org>, Miguel Garcia <miguelg@google.com>, "Peter Beverloo" <beverloo@google.com>
On 08 Jan 2014, at 16:03, Bassbouss, Louay <louay.bassbouss@fokus.fraunhofer.de> wrote: > Hi Ansi, > > My proposal addresses a new mechanism rather than new use cases. Using this mechanism, developers don't need necessary to put the second screen content in an separate html document and control it e.g. using post messages. [...] Thanks for the clarification. IIUC, it sounds like what you’re describing could be implemented with the existing API. One could come up with a JavaScript library built atop the current API, that would construct the DOM on the secondary display based on a subtree of the DOM on the primary screen. Thanks, -Anssi
Received on Wednesday, 8 January 2014 14:31:11 UTC