Re: [whatwg/fullscreen] Remove top layer definitions, now that CSS Position 4 contains them. (PR #223)

Thanks @tabatkins, this now builds!

I've poked https://github.com/whatwg/fullscreen/pull/204 to see if we can get that landed, although it doesn't block this PR.

I think we can put interactions between fullscreen and other top layer-using features to the side, since as you point out `<dialog>` already can't go fullscreen, and popovers are new so there's no site compat risk to consider.

That leaves pure uses of the Fullscreen API with multiple elements. I think the conservative thing to do is to conserve the existing behavior where we move an element within the top layer. I'm not aware of real-world uses of it, but it's not especially far-fetched and the web is big.

I think the most straightforward approach is to call "remove an element from the top layer immediately" followed by " an element to the top layer", is that what you think we should do?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fullscreen/pull/223#issuecomment-1522104683
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fullscreen/pull/223/c1522104683@github.com>