- From: Richard Bushell <notifications@github.com>
- Date: Tue, 26 Feb 2019 18:35:08 +0000 (UTC)
- To: whatwg/fullscreen <fullscreen@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 26 February 2019 18:35:31 UTC
Apologies, I don't know if you are taking comments from third-parties, but +1 for: element.requestFullscreen({ replace: true }) document.exitFullscreen({ fully: true }) or similar functionality. And maybe a readable array of LIFO fullscreen elements? The current state of browser handling of nested fullscreen elements is a disaster. For example, a single-page website that might have the HTML element fullscreen and then also allow a video element within it to go fullscreen. Without adding some extra tools to the Fullscreen API the current situation is intolerable! -- 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/70#issuecomment-467558352
Received on Tuesday, 26 February 2019 18:35:31 UTC