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

@mfreed7 I think that preserving the "In other words, element is moved to the end of top layer if it is already present" behavior of the current spec has some merits. It makes for a less strange API, avoiding the situation where a request appears to succeed but it doesn't actually change anything.

For dialogs and popovers, is there any reason they shouldn't also allow this flip-flopping behavior? I don't want to go overboard with consistency, just want to check.

An important difference between fullscreen and the other features is that going fullscreen is async so the synchronous checks that `elm.showPopover()` and `dialog.showModal()` have aren't enough, there's also checks after resizing the window. So going fullscreen has the style of pre-flight check, try to do it, then deal with weird things that happened. This is all to say I think it would be OK if fullscreen is slightly different to the others in this regard.

Thoughts.

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

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