Philip Jägenstedt

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

@upsuper, can you take a look at https://github.com/whatwg/fullscreen/pull/64? Not all error cases are handled, and even figuring out what they all are is tricky. I'll try to tinker with this...

A request can fail with a fullscreenerror event, so I've also tested what events are fired for the "request then exit+request" case after clicking "exit+request" with a [variation](https://gist.github.com/foolip/c333ab539685bebc0e53d1808ce4aa21) on the...

@annevk, do you care either way about how all of this behaves, or is anything fine as long as we get interop?

Yeah. I think the first option from https://github.com/whatwg/fullscreen/issues/63#issuecomment-261948581 has a simplicity of sorts, but avoiding cycles of entering and exiting would require some ugly checks that make it pointless. Another...

Blink used to have an exemption for `video.webkitEnterFullscreen` which included native video controls, but I managed to removed it: https://codereview.chromium.org/1237133002 https://codereview.chromium.org/1240573005

That is what I'm talking about too, the change "included native video controls." The context menu for video doesn't allow going fullscreen.

@duanyao, was there something you were trying to build when you ran into this? The "if a user click a link/button to navigate to a slide show page, he/she still...

Allowing any page to go fullscreen on initial load is more than would be required to solve the use case @duanyao describes I think. It's simpler than other solutions we...

Do you mean something like this? ``` JavaScript document.onclick = function() { var win = window.open(); win.document.body.requestFullscreen(); } ```