- From: Philip Jägenstedt <notifications@github.com>
- Date: Thu, 18 May 2017 05:30:05 -0700
- To: whatwg/fullscreen <fullscreen@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 18 May 2017 12:30:37 UTC
On exiting fullscreen in Blink, the fullscreen element is the target, even if that's not the only element in top layer. It's a very good point about the hierarchy restrictions, which Blink still has. If we get rid of those, then it'll be very hard to guarantee that each element gets a pair of fullscreenchange events. At this point I would be fine with adding back the hierarchy restrictions. They seemed artificial after the fullscreen element stack was merged into top layer, but if they make the model simpler, then that's simpler :) (Another case I've noticed is that when exiting from nested fullscreen, there's actually no guarantee that the iframe is still the topmost fullscreen element in the ancestor document, but the spec doesn't handle that.) -- 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/89#issuecomment-302389588
Received on Thursday, 18 May 2017 12:30:37 UTC