- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Thu, 21 Jun 2012 07:18:52 -0400
- To: ext Anne van Kesteren <annevk@annevk.nl>, fantasai <fantasai.lists@inkedblade.net>, Daniel Glazman <daniel.glazman@disruptive-innovations.com>
- CC: Peter Linss <peter.linss@hp.com>, Chris Lilley <chris@w3.org>, public-webapps <public-webapps@w3.org>, "www-style@w3.org" <www-style@w3.org>
On 6/21/12 5:16 AM, ext Anne van Kesteren wrote: > On Tue, Jun 19, 2012 at 10:48 PM, fantasai > <fantasai.lists@inkedblade.net> wrote: >> You could just work in the explanation I sent in >> http://www.w3.org/mid/4FC64100.3060800@inkedblade.net > Added a note. > > The reason this is not very elaborated is that this really belongs in > a CSS specification that defines the layout box model and painting > order etc. in detail. As part of that you would have the top layer > concept and ways to hook into it via pseudo-elements, such as > ::backdrop. And some non-normative description around it to aid people > new to the material. > > Having this in Fullscreen is just patching holes in the CSS 2.1 > specification, which is not a great way to do things. Daniel, Fantasai - please confirm whether or not Anne's latest changes ([1],[2]) address the "#2 issue" ([3]) that is blocking FPWD: <https://dvcs.w3.org/hg/fullscreen/raw-file/tip/Overview.html#::backdrop-pseudo-element> -Thanks, AB [1] https://dvcs.w3.org/hg/fullscreen/rev/41052063ef66 [2] https://dvcs.w3.org/hg/fullscreen/rev/23f36a1db497 [3] http://lists.w3.org/Archives/Public/public-webapps/2012AprJun/1252.html
Received on Thursday, 21 June 2012 11:19:49 UTC