[Bug 26366] It's possible to go fullscreen with an element not in the document

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26366

--- Comment #1 from Philip Jägenstedt <philipj@opera.com> ---
I did some ad-hoc testing on calling requestFullscreen() and exitFullscreen()
multiple times in the same script and found that there wasn't great
interoperability even when one doesn't try to circumvent the checks.

The basic problem is that the script-visible fullscreen element stack shouldn't
be updated until one has actually entered/exited fullscreen, and there's no
script-invisible state available to do these checks.

I can see a few options:

1. Have a script-invisible stack of pending requests which is pushed to the
script-visible stack before the fullscreenchange event is fired.

2. Have a single pending element which is replaced by successive calls to
requestFullscreen().

3. Make requestFullscreen() and exitFullscreen() do nothing if there's already
a pending change.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 28 July 2014 09:22:11 UTC