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

@upsuper - I have tested your proposed CSS selector workaround, but unfortunately the :fullscreen pseudo-class seems to only ever match ONE element (the current fullscreenElement at the top of the fullscreen stack). Here's my test:-

https://living.video/fullscreenchange.html

I used the same test to double-check the fullscreenchange listeners at both Element and Document level too. If you view the page source then it's pretty self-explanatory. Just view the Console to see the Event activity.

Current browser adherence to the spec is mixed. Blink & Gecko seem perfect. Edge does not fire fullscreenchange at the Nested Video Player element when it EXITS fullscreen from the nested element. Safari Webkit has a major bug which I've already filed, i.e. that as soon as you enter fullscreen on a nested element it returns NULL as the fullscreenElement (breaking everything).

But, in the base context of the further discussion arising in this thread, I believe there is still no way to know if there are multiple/nested elements in the fullscreen stack. You could only discover them by popping each in turn. So, I believe my earlier comment about not having any exposure to the fullscreen stack, or even it's length, is still correct (unless I've mis-implemented the method, or unless there's another way?)

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