Re: [whatwg/fullscreen] Decide whether to resize synchronously in requestFullscreen() (#64)

Thanks, @upsuper, that's very helpful. Is this queue in the same process/thread as the rendering engine, i.e. can you inspect its state synchronously in `requestFullscreen()`?

Are you currently synchronizing "apply the fullscreen request" with animation frames, or does it happen whenever the resize is reported to be done?

> Having written this down, I wonder whether this is the only reason we reject when element is moved to a different document. If so, I guess we probably don't really need that restriction.

Yes, keeping track only of *topLevelDoc* would for for #33. Using *pendingDoc* amounts to a pretty harmless restriction though, so I wouldn't mind aligning with that if it'd be simpler for you.

> We should probably be recording the top level document instead, otherwise it would still be an issue that the requesting document can be moved to a different top level document.

I don't think it's possible to move documents, here's a test that shows that moving an iframe causes its document to change: https://software.hixie.ch/utilities/js/live-dom-viewer/saved/4693

In addition to all of the above, can you elaborate on how exiting works? Do exits also end up in the same queue, and how are competing requests and exists handled? I would like the spec to match Gecko in https://github.com/whatwg/fullscreen/issues/63, so if you have a good model we can just copy it exactly :)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fullscreen/pull/64#issuecomment-263055537