W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2011

[whatwg] Fullscreen revision I

From: Anne van Kesteren <annevk@opera.com>
Date: Mon, 14 Nov 2011 13:27:35 +0100
Message-ID: <op.v4xrj9qf64w2qv@annevk-macbookpro.local>
Sorry for the late reply. Getting to and from TPAC and TPAC itself is  
basically the reason. I hope you understand.

On Wed, 26 Oct 2011 04:06:28 +0200, Robert O'Callahan  
<robert at ocallahan.org> wrote:
> When you say "No longer any attempts at integrating with "F11  
> fullscreen"", do you mean to rule out the possibility that UAs do that?  
> E.g., would you
> allow UAs to have UI that makes the current document fullscreen and sets  
> the fullscreen element to the root element?

If UAs want to implement such UI I think that should be fine. However  
today F11 allows for navigation and such, which this mode does not.


About your nested-fullscreen proposal, I do not see how

> To fix the nested cases, I suggest having a per-document stack of  
> fullscreen elements instead of a single "fullscreen element". [...]

combines with

> 2.2 Pop the top element off D's fullscreen element stack until the stack  
> is empty or the element at the top of stack is in D

as supposedly everything on D's stack would be in D. Should  
D.exitFullscreen not just pop one of D's stack and if that stack is empty  
at that point also clear any descendant document stacks? The only tricky  
thing there might be order (of events). E.g. if you have a descendant B  
which has two descendants each with a fullscreen element. I guess you can  
do them based on the stack order of B.


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Monday, 14 November 2011 04:27:35 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:09 UTC