- From: Philip Jägenstedt <notifications@github.com>
- Date: Fri, 25 Nov 2016 10:30:29 -0800
- To: whatwg/fullscreen <fullscreen@noreply.github.com>
- Message-ID: <whatwg/fullscreen/pull/64/review/10194364@github.com>
foolip commented on this pull request. > + + <p class=note>For example, <var>pending</var> may have been moved to another document, + <code>allowfullscreen</code> attributes may have been removed, or <var>topLevelDoc</var> may + have exited fullscreen since {{Element/requestFullscreen()}} was invoked. + + <li> + <p>If <var>error</var> is true, run these subsubsteps: + + <ol> + <li><p><a>Fire an event</a> named <code>fullscreenerror</code> on <var>pendingDoc</var>. + + <li><p>Reject <var>promise</var> with a <code>TypeError</code> exception. + + <li><p>Terminate these steps and run the remaining subsubsteps <a>in parallel</a>. + + <li><p>If <var>resize</var> is true, resize <var>topLevelDoc</var>'s viewport to its "normal" It would be a case like this: ```JavaScript button.addEventListener('click', () => { a.requestFullscreen(); b.requestFullscreen() b.remove(); }); ``` Both requests will try to resize, and per spec it's a racy situation, but let's assume that after the resize the animation frame task for *a* runs first and *a* becomes the fullscreen element. Then *b* will end up in this situation, exiting fullscreen, but *a* will still be the fullscreen element. -- 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
Received on Friday, 25 November 2016 18:31:35 UTC