W3C home > Mailing lists > Public > public-coremob@w3.org > June 2012

Re: coremob-ISSUE-8: No spec to point to for Full-screen mode. [COREMOB-1]

From: Tobie Langel <tobie@fb.com>
Date: Wed, 20 Jun 2012 08:49:55 +0000
To: Scott Wilson <scott.bradley.wilson@gmail.com>
CC: Robin Berjon <robin@berjon.com>, Charles McCathieNevile <chaals@opera.com>, W3C CoreMob CG <public-coremob@w3.org>
Message-ID: <CC075AC6.8FD41%tobie@fb.com>
On 6/20/12 8:06 AM, "Scott Wilson" <scott.bradley.wilson@gmail.com> wrote:
>>> On 19 Jun 2012, at 10:36, Robin Berjon wrote:
>>>> Actually, we have to think a little bit beyond this being equal to
>>>> view-mode=fullscreen. On (most) mobile devices, since every
>>>> is always full screen, when you remove the chrome you get a full
>>>> application. But on anything that has an windowing system, there's a
>>>> difference. I think that what's wanted here is view-mode=chromeless,
>>>> which in a windowed environment would give you an app without chrome
>>>> not necessarily occupying the entire screen.
> Isn't that a good fit for viewmode:floating from VMMF?
> "Describes a Web application providing a more immersive interface,
>running in a windowed manner but without chrome, and with the viewport's
>initial background being transparent such that other system items (other
>applications, the display's background...) can be seen through parts of
>the viewport that are not being painted to."
> For smaller devices, or those with no concept of windowing, a viewmode
>preference of "floating" could fallback to "fullscreen".

Advising mobile web developers their apps are going to run in "floating"
mode isn't going to fare very well. Clownesque is the word that comes
mind. :)

>>>> And, of course, a way of
>>>> requesting that a given view-mode be activated.
>There have been a few times I'd have liked this, but I think the method
>of letting the user and UA control the viewmode and have the content
>adapt seems more appropriate. If apps did have the ability to request a
>viewmode change is fairly likely to be suboptimal, as the app developer
>likely has a preconceived notion of the type of device and capabilities
>its running on, which may conflict with the preferences of the user.

This is another argument for separating chromelessness (heh!) from
view-mode. Clearly, the app's ability to run without chrome is something
only the app author knows about.

It's also obvious that view-mode is not something the app should be able
to choose. It's something the environment (and the user) imposes on the
app and lets it know about (through media queries).

The implications for view-mode is that:

    @media (view-mode: fullscreen) { /* ... */ }

becomes technically the same thing as:

    @media (view-mode: maximized) and chromeless { /* ... */ }

Received on Wednesday, 20 June 2012 08:50:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:05:47 UTC