On Sun, 31 Jan 2010 03:43:49 +0100, Simon Fraser <s...@me.com> wrote:
On Jan 30, 2010, at 1:24 PM, Anne van Kesteren wrote:
To stop polluting the Window object, might it make sense to put the new
members (other than event handler attributes) on window.screen?
This would require that the current window object is passed implicitly
to the method, so the UA knows which window to take fullscreen, right?
Isn't the Screen object always associated with a single Window object?
I.e. there's a 1:1 mapping.
This talk of going into fullscreen on different screens at the same time
makes me think that the screen should be an optional argument:
void enterFullscreen(optional DOMElement element, optional Screen,
optional boolean enableKeys);
with the default screen being either the main screen, or window.screen.
As far as I know there is no API to that deals with multiple monitors
currently. This is a minor issue with e.g. Media Queries, the Screen
object, etc.
--
Anne van Kesteren
http://annevankesteren.nl/
