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

Can you explain what experiment you could run to determine whether (2)
happens synchronously or asynchronously?

 On Jul 28, 2014 9:03 AM, "Anne van Kesteren" <> wrote:

> 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>
> boundaries?)
> 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:
> * (It's possible
> to go fullscreen with an element not in the document)
> * (Allow
> fullscreenchange events to be synchronized with animation frames)
> --

Received on Monday, 28 July 2014 17:43:18 UTC