- From: Philip Jägenstedt <notifications@github.com>
- Date: Thu, 17 May 2018 15:58:42 +0000 (UTC)
- To: whatwg/fullscreen <fullscreen@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 17 May 2018 15:59:05 UTC
> @foolip indicated that ordering doesn't matter between fullscreenchange and resize on a chat with him so I think this approach is easier to understand. At risk of contradicting myself, it could matter for web compat and having the same event order when exiting with `document.exitFullscreen()` and `document.fullscreenElement.remove()` would be nice, but it doesn't seem like perfect alignment is possible here. The problem https://github.com/whatwg/fullscreen/pull/102 was supposed to solve and what we got stuck on is that when removing the fullscreen element, we sometimes have to exit fullscreen, but the "exit fullscreen" algorithm is async and depends on the state that was synchronously changed by removing the node. So something special needs to happen. -- 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/126#issuecomment-389917989
Received on Thursday, 17 May 2018 15:59:05 UTC