- From: Xidorn Quan <notifications@github.com>
- Date: Wed, 29 Aug 2018 21:41:15 -0700
- To: whatwg/fullscreen <fullscreen@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 30 August 2018 04:41:37 UTC
Oh... I indeed didn't pay much attention on this side. What Gecko currently does is that, we have an internal (non-web-exposed) CSS property `-moz-top-layer`, which we apply value `top` for `:fullscreen:not(:root)`. And when the property is set to `top`, we apply the styling magic (specifically set `position` to `absolute` when it's not `fixed`), and we only render such elements in the top layer. So the observation is correct that Gecko doesn't put the document element in the top layer for rendering purpose, but Gecko does indeed put that element into the top layer stack for other purpose (and the stack is still called "fullscreen stack" in Gecko currently since that's still the only thing it's serving). It's not clear what's the best way to spec this. Maybe change > Each element and ::backdrop pseudo-element in a top layer has the following characteristics: to something like > Each element excluding the document element, and ::backdrop pseudo-element in a top layer has the following characteristics: -- 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/134#issuecomment-417187840
Received on Thursday, 30 August 2018 04:41:37 UTC