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

[presentation-api] Define behavior of Window and Fullscreen APIs in the presentation browsing context

From: Mark Foltz via GitHub <sysbot+gh@w3.org>
Date: Mon, 01 Jun 2015 18:23:04 +0000
To: public-secondscreen@w3.org
Message-ID: <issues.opened-83633033-1433182984-sysbot+gh@w3.org>
mfoltzgoogle has just created a new issue for 
https://github.com/w3c/presentation-api:

== Define behavior of Window and Fullscreen APIs in the presentation 
browsing context ==
I think some normative statements about the behavior of these APIs 
should be considered. 

First, APIs that require input or handle focus should be discouraged 
from being supported:
* alert()
* confirm()
* blur()
* focus()
* print()
* prompt()

APIs that create new browsing contexts also be discouraged, as they 
are not friendly with 1-UA presentation.
* open()
* createPopup()

APIs that modify the position of the window are also not very 
meaningful in a reasonable implementation of the 1-UA mode:
* moveTo()
* moveBy()
* resizeTo()
* resizeBy()

Finally, we should support the  [Fullscreen 
API](https://fullscreen.spec.whatwg.org/), as web developers may want 
to use related CSS features as well as ensure fullscreen rendering of 
`<video>` content.  However, we may need to patch the Fullscreen spec 
for this scenario - need to dig further.








See https://github.com/w3c/presentation-api/issues/99
Received on Monday, 1 June 2015 18:23:05 UTC

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