- From: Philip Jägenstedt <notifications@github.com>
- Date: Mon, 29 Jan 2018 07:25:31 -0800
- To: whatwg/fullscreen <fullscreen@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 29 January 2018 15:25:58 UTC
Video inside a presentation is the canonical use case, yeah. Nested fullscreen is indeed a source of complexity, alongside fullscreen in iframes and the hand-wavy cross-process stuff. However, note that https://github.com/whatwg/fullscreen/pull/102 would still be annoying without nested fullscreen, the root problem there is that elements are removed from top layer in between the sync and async part of the exit fullscreen steps. I think that from a web developer's perspective, it'd seem weird that nested elements don't work, but that nested iframes do. Iframes is definitely something that needs to keep working. I can still add a use counter though. -- 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/119#issuecomment-361280138
Received on Monday, 29 January 2018 15:25:58 UTC