- From: Anssi Kostiainen via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 Jun 2015 13:11:34 +0000
- To: public-secondscreen@w3.org
Given the new information from real world usage (thanks @mfoltzgoogle), I suggest we keep this issue open and explore alternative techniques that would maintain backwards compatibility with existing web content without compromising the user's security and privacy. I'll start with a couple of proposals (not necessarily good ones) to restart the discussion: * Expand (or patch) the semantics of the `allowfullscreen` attribute to allow also the Presentation API usage in addition to the Fullscreen API, if set to true. Technically, the content to be presented on a second screen is often fullscreen. By doing this, we'd lose the ability to say the nested content can be made fullscreen on the primary screen but not shown on any of the secondary screens, and vice versa. * Leave it up to the implementation to ask for user's consent and make it explicit that nested content would like to present itself on a secondary screen. Would mean all the web pages with nested content out there could make use of the Presentation API. However, this behaviour would not be a testable assertion in the spec and to that end conformant but otherwise bad quality implementations might compromise users' security and privacy. Also, it may be hard to implement this in a way that a normal user does not get confused. -- GitHub Notif of comment by anssiko See https://github.com/w3c/presentation-api/issues/79#issuecomment-108893408
Received on Thursday, 4 June 2015 13:11:36 UTC