W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: CfC: publish FPWD of Fullscreen spec; deadline May 24

From: fantasai <fantasai.lists@inkedblade.net>
Date: Tue, 19 Jun 2012 13:36:44 -0700
Message-ID: <4FE0E2DC.6040201@inkedblade.net>
To: Anne van Kesteren <annevk@annevk.nl>
CC: www-style@w3.org, "public-webapps@w3.org" <public-webapps@w3.org>
On 06/19/2012 12:40 AM, Anne van Kesteren wrote:
> On Tue, Jun 19, 2012 at 1:31 AM, fantasai<fantasai.lists@inkedblade.net>  wrote:
>> On 06/01/2012 05:02 AM, Anne van Kesteren wrote:
>>> On Wed, May 30, 2012 at 5:47 PM, fantasai<fantasai.lists@inkedblade.net>
>>>   wrote:
>>>> Though it seems likely that 'fixed' is required here, no?
>>> The top layer concept is also used by HTML for its<dialog>    element.
>> This response doesn't seem to match the quoted sentence. ??
> For fullscreen it is set to fixed per the default rendering rules. We
> do not want to do that all the time because HTML<dialog>  uses the
> same rendering concepts.

Hm, so if I scroll with a fullscreened <dialog>, the dialog scrolls
out of view, but if I scroll with a fullscreened <img>, the image
stays in view?

>>> I expect we'll just update the specification.
>> If it's still actively edited at that point, sure.
> If it's not maintained it's dead and unreliable anyway...

How unreliable it is depends on how stable it became before it was abandoned.
It doesn't hurt to word things in ways that will remain true once you are
busy working on something else; rather it helps the spec remain reliable to
reduce the dependencies on the exact details of other specs.

>> You also need to state its relationship to other elements in the tree.
>> Right now its inheritance behavior is undefined.
> Why? It has no children.

Sure, that's fine. Might make it explicit, but really the issue is what
element does the ::backdrop element inherit from?

Received on Tuesday, 19 June 2012 20:37:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:34 UTC