W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2010

[whatwg] api for fullscreen()

From: Robert O'Callahan <robert@ocallahan.org>
Date: Fri, 29 Jan 2010 17:43:34 +1300
Message-ID: <11e306601001282043g5bdf73c4k7f929d69eb4b425b@mail.gmail.com>
On Fri, Jan 29, 2010 at 4:06 PM, Kit Grose <kit at iqmultimedia.com.au> wrote:

> Regarding point 1, surely any fullscreen API should only support
> block-level elements?
>

I don't see why. Setting position:fixed does what you want in the cases I
can think of.

If I'm reading point 2 correctly, I disagree with it (except in cases like
> <video> where a default style exists to manipulate the element itself). To
> me (based on how I can envisage using this functionality, particularly
> regarding touch-screen kiosks) the use-cases for full-screen capable
> elements should be left out of the UA and in the hands of the author (e.g.
> as Javascript buttons or links).
>

Sorry I wasn't clear. By "in-page UI" I meant UI under the control of the
author.

When it comes to point 3, I figure a good way to handle this might be to
> introduce a CSS pseudo-class for fullscreen elements. Then the UA default
> style would simply be *:fullscreen { position: fixed; left: 0; top: 0;
> right: 0; bottom: 0; }. Some method for changing the layout of the element
> is going to be required to handle cases where the aspect ratio of the screen
> doesn't match that of the element in the document flow.
>

Indeed. A CSS pseudo-class sounds like a reasonable idea.

Should zoomed-up versions of a container scale elements like images and text
> or merely the containing box? If the latter, does that limit the ability to
> provide animation in-UA to naturally zoom the element to full-screen without
> distracting re-flow of text? And does it limit the likely use-case for
> authors of providing full-screen slideshows etc. where images would be
> expected to zoom to fill their new, larger container.
>

If you change the layout, zooming isn't really necessary. My guess is that
there are several interpolation strategies for transition effects that would
all work. For example, you could apply the style change, render the element
at the size of the screen, and then zoom that image out from the element's
old position to the screen size.

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
53:5-6]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20100129/19458717/attachment.htm>
Received on Thursday, 28 January 2010 20:43:34 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:20 UTC