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

@foolip

No problem signing the agreement if any ideas or solutions are implemented into the spec.  The fundamantal problem is that, to my understanding, the Browser UA has information about the fullscreen stack that is unavailable to the developer.  In particular, the developer has no way that I am aware of to query if there are more than one elements in fullscreen concurrently, which is essential in making certain decisions.  Currently, you cannot read/get in advance whether there are multiple elements nested/stacked.  If there was a way to read/get that information, then desired actions based on that state can be actioned to a plan.  For instance, why not allow a getter for document.fullscreenElements (plural) to return a read-only array of elements, and by extension document.fullscreenElements.length?  Optionally, even a readable property like .isFullscreen on each element too?  Optionally, even allow element.exitFullscreen (at Element level, wherever it is in the stack) to counter the current element.requestFullscreen method.  I think that many fundamental issues to the developer could be circumvented by exposing the multiple elements (or at least knowledge/number of them).  That would be my desired solution, BUT failing that exposure, then "element.requestFullscreen({ replace: true })" or "document.exitFullscreen({ fully: true })" provide a much easier method to take control of the current situation of the fullscreen elements stack.  Obviously, in terms of spec only, I am trying to avoid detailing the current mess of implementation across browsers.

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