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

Given https://github.com/whatwg/fullscreen/pull/64#discussion_r89648822 and that `exitFullscreen()` has a similar race, I think that the approach in the PR won't quite work.

In order to make it well defined what happens with racing resizes and which order all the promises are resolved, I think we'll need to have some state on the top-level browsing context, or *some* kind of queue of requests. For at least exits, I think that all requests will also have be handled in a single animation frame task following the resize, otherwise some promises can't be resolved in the same tasks where the corresponding events are fired.

What do you think, can it be simpler and still completely well defined?

-- 
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-263010550