W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2010

[whatwg] Feedback on the Mozilla FullScreen API proposal

From: John Harding <jharding@google.com>
Date: Sun, 8 Aug 2010 22:58:17 -0700
Message-ID: <AANLkTinAkUD8UPCZkOXakWByk-5j8DL3AcrrVgnQwEV-@mail.gmail.com>
If there are multiple elements on the page (e.g. multiple inline video
players) that could go fullscreen, you still need some way to determine
which of them the user intended to make fullscreen.  My understanding is
that was the point of designating a fullscreen element - it still requires
that elements cooperate (by checking to see that they are the intended
fullscreen element), but it's possible for them to do the right thing.
If fullscreen was initiated at the document level, then the intended
behavior is ambiguous, and I would expect none of the elements to go
fullscreen.

-John

On Sun, Aug 8, 2010 at 10:50 PM, Robert O'Callahan <robert at ocallahan.org>wrote:

> Fullscreen support for specific elements is more than just a convenience -
> it's fairly common to have multiple elements on a page that could be made to
> go fullscreen
>
> If the browser fullscreen API only supported making the entire page
> fullscreen, you could make an element fullscreen by making the page
> fullscreen and then making the element fill the page.
>
> This is in fact what the proposed API does. It just provides a convenient
> way for authors to achieve it.
>
>
> Rob
> --
> "Now the Bereans were of more noble character than the Thessalonians, for
> they received the message with great eagerness and examined the Scriptures
> every day to see if what Paul said was true." [Acts 17:11]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20100808/70ebac55/attachment-0001.htm>
Received on Sunday, 8 August 2010 22:58:17 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:59 UTC