- From: Mason Freed <notifications@github.com>
- Date: Tue, 02 May 2023 12:56:00 -0700
- To: whatwg/fullscreen <fullscreen@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 2 May 2023 19:56:06 UTC
> To get the equivalent behavior for the fullscreen API, we should reject if the element is already in top layer stack, but we shouldn't add back a hierarchy restriction. > > @josepharhar @mfreed7 would that work for you? If this ends up being web compatible, I'm definitely supportive. It feels right to: 1. Try to match other top layer APIs like dialog and popover, generally. That includes: 2. Reject/throw/no-op when a "second" top layer API call is made while an element is already in the top layer. 3. Allow fullscreen to be flexible and not require elements to be DOM-nested in order to both use fullscreen. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fullscreen/pull/223#issuecomment-1532064486 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fullscreen/pull/223/c1532064486@github.com>
Received on Tuesday, 2 May 2023 19:56:06 UTC