Re: [whatwg/fullscreen] Introduce document.exitFullscreen({ fully: true })? (#70)

> Assuming CSS selectors (when fixed/implemented) then offer a mechanism to have knowledge of multiple fullscreen elements, could their ORDER be determined?

`querySelectorAll` is guaranteed to return elements in the tree order, and in Firefox currently, you can only nestedly fullscreen an element only if it's a descendant of the current fullscreen element (which is the hierarchy restriction I mentioned before), so the order is guaranteed to be from the bottommost to the topmost fullscreen element.

If we remove the hierarchy restriction, the tree order may not be that useful to determine the order in top layer. But for other reasons, I would argue that we should enforce the hierarchy restriction. But that's a separate topic.

-- 
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-469065454