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

[whatwg] Fullscreen CSS

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 15 Nov 2011 12:10:09 +1300
Message-ID: <CAOp6jLZdFNwKZx+TTOqi=TSYLmycRxrePNKUjU7Hq8mOuUkB0g@mail.gmail.com>
On Tue, Nov 15, 2011 at 10:54 AM, Tab Atkins Jr. <jackalmage at gmail.com>wrote:

> I think we should go the route that the <dialog> element did in Ted's
> change proposal and have a pseudo-element that gets created when an
> element is fullscreened.  Simple and easy, and trivial for the author
> to manipulate to get most effects they could want.
>

Interesting. I did not know about that.

That proposal requires layout engine changes --- specially, at least one
new rule for CSS stacking contexts in the infamous "appendix E". Also, it
doesn't address situations where an ancestor of the <dialog> or fullscreen
element has 'opacity', 'transform', 'filter', 'mask' or 'clip-path' (and
maybe other things I've forgotten).

I think we should probably define a unified mechanism that can be used for
the fullscreen element and the <dialog> element and anything else like it
we need. And figure out what happens if you make part of a page fullscreen
and that uses <dialog>. Or if you have nested <dialog>s mixed with
fullscreen... Hmm.

Rob
-- 
"If we claim to be without sin, we deceive ourselves and the truth is not
in us. If we confess our sins, he is faithful and just and will forgive us
our sins and purify us from all unrighteousness. If we claim we have not
sinned, we make him out to be a liar and his word is not in us." [1 John
1:8-10]
Received on Monday, 14 November 2011 15:10:09 UTC

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