W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2012

[whatwg] Fullscreen changes to support <dialog>

From: Anne van Kesteren <annevk@opera.com>
Date: Wed, 04 Apr 2012 19:39:45 +0200
Message-ID: <op.wb84ojot64w2qv@annevk-macbookpro.local>
On Wed, 04 Apr 2012 19:31:22 +0200, Tab Atkins Jr. <jackalmage at gmail.com>  
wrote:
> On Wed, Apr 4, 2012 at 1:05 AM, Anne van Kesteren <annevk at opera.com>  
> wrote:
>> How does this work for nested browsing contexts? Currently using <iframe
>> allowfullscreen> (not in HTML yet) you can fullscreen elements embedded  
>> via an <iframe>. Would we then have to push the <iframe> element on the  
>> stack and make its height and width cover the viewport, and then push  
>> the element in question inside the <iframe> on the stack, or do we want  
>> to deal with
>> this in another way?
>
> The thinking so far is that we don't do anything special for dialogs.
> They don't escape their <iframe>, and the <iframe> doesn't have any
> special response to a dialog spawning within it, unlike for
> fullscreen.

That's why I was asking for what I should do with fullscreen :-)


> :fullscreen::backdrop {
>  position: fixed;
>  top: 0; left: 0; right: 0; bottom: 0;
>  background: black;
> }

Hixie's proposal mentioned you could only style background related  
properties for this pseudo-element. But okay, all seems easy enough.


> As far as I can tell, you're right that we no longer need the
> :fullscreen-ancestor pseudo.

Yay, it was ugly.


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Wednesday, 4 April 2012 10:39:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:07 GMT