Re: [whatwg/fullscreen] Decide on wanted behavior for request+exit or exit+request together (#63)

Possible models:
 1. All `requestFullscren()` and `exitFullscreen()` calls go on a single cue, and are processed in order. (Would match Edge in the simple cases tested.)
 1. Keep track of pending resizes and reject any attempt to go in the other direction until done. (Would match Firefox in the simple cases tested.)
 1. In `requestFullscreen()`, attempt no resize if pending's top-level browsing context’s active document’s fullscreen element is not null, so that if already in fullscreen or if currently exiting, it does nothing. Then handle the "unexpected" case of having already exited in the animation frame task. (Would also match Firefox in the simple cases tested.)

Others?

The first is simple in some sense, but would enable long series of transitions in and out of fullscreen, pointless from the user's perspective. The second or third seems simpler to implement in Blink at this time.

-- 
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/issues/63#issuecomment-261948581