W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2014

[whatwg] Fullscreen API and out-of-process <iframe>

From: Anne van Kesteren <annevk@annevk.nl>
Date: Mon, 28 Jul 2014 18:03:35 +0200
Message-ID: <CADnb78iSx0d6OPHZean+i0bnhfHXrih54stGXXBgY5Huj_Z6Rg@mail.gmail.com>
To: WHATWG <whatwg@whatwg.org>, "Robert O'Callahan" <rocallahan@mozilla.com>, Adam Barth <w3c@adambarth.com>, Philip J├Ągenstedt <philipj@opera.com>, Vincent Scheib <scheib@google.com>
There's two things the Fullscreen API does:

1. Resize the top-level browsing context's document's viewport. (I.e.
resizing the window of the browser.)
2. Change state of that document and its descendant documents.

1 needs to happen asynchronously. 2 needs to happen from a task
per-document. Potentially 2 could happen from a task per unit of
related browsing contexts, but I'm not sure if that's better. 2 also
needs to be synchronized with animation frames, once we figure out how
to define that. (How are animation frames synchronized across <iframe>

I don't really see a way to avoid having a global flag across process
boundaries. E.g. if B is nested through A (assume allowfullscreen is
set), A and B are cross-origin, and both invoke requestFullscreen(),
what happens? (YouTube embedded in some other app.)

Anyone with a good idea how we could make this work?

There's some background on some of this available here:
* https://www.w3.org/Bugs/Public/show_bug.cgi?id=26366 (It's possible
to go fullscreen with an element not in the document)
* https://www.w3.org/Bugs/Public/show_bug.cgi?id=26440 (Allow
fullscreenchange events to be synchronized with animation frames)

Received on Monday, 28 July 2014 16:04:09 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:22 UTC