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

@upsuper - You are right! Apologies, I didn't re-run my own initial test on Firefox after I made a final tweak earlier to the code to handle all prefixed and non-prefixed selectors.

Yes, Firefox is indeed the only browser that implements the current spec correctly, and therefore is currently the only browser that allows a developer to to know if there are multiple (nested) fullscreen elements, by querying all elements matching the CSS :fullscreen selector.

@foolip - have you got an inner channel within Google to chase this through for Chrome?  Blink seems compliant in every other respect that I can see.

@jernoble - have you got an inner channel to chase the Fullscreen API issues with Webkit through? The CSS selector issue isn't disastrous, BUT the issue where WebKit sets the fullscreenElement to null as soon as trying to enter a nested/secondary fullscreen capable element is a major problem, and has just been exposed to a much larger audience for Apple since implementing the Fullscreen API on iPad in the last couple of weeks. This would probably break all affected websites.

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

Finally, please let me know your final decision on document.exitFullscreen({ fully: true }) once you've all had a chance to discuss, this would be a really useful option for developers.

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