W3C home > Mailing lists > Public > public-coremob@w3.org > January 2013

Re: New draft of Coremob-2012 published, plus what's next

From: Lars Erik Bolstad <lbolstad@opera.com>
Date: Thu, 24 Jan 2013 11:26:56 +0100
Message-ID: <51010C70.3070406@opera.com>
To: Charles McCathie Nevile <chaals@yandex-team.ru>
CC: Tobie Langel <tobie@fb.com>, Dominique Hazael-Massieux <dom@w3.org>, Jo Rabin <jo@linguafranca.org>, "public-coremob@w3.org" <public-coremob@w3.org>
Den 24.01.13 08:03, skrev Charles McCathie Nevile:
> On Thu, 24 Jan 2013 13:28:13 +0400, Lars Erik Bolstad 
> <lbolstad@opera.com> wrote:
>
>> Den 24.01.13 07:28, skrev Tobie Langel:
>>> On Jan 23, 2013, at 23:22, "Charles McCathie Nevile" 
>>> <chaals@yandex-team.ru> wrote:
>>>
>>>> On Wed, 23 Jan 2013 20:01:50 +0400, Dominique Hazael-Massieux 
>>>> <dom@w3.org> wrote:
>>>>
>>>>> Le mercredi 23 janvier 2013 à 15:48 +0000, Tobie Langel a écrit :
>>>>>
>>>>>>> * I think Req 12 is addressed by the "view-mode" media feature with
>>>>>>> value "fullscreen"
>>>>>>> http://www.w3.org/TR/view-mode/#the--view-mode--media-feature 
>>>>>>> (but I > may be missing a subtlety)
>>>>>> Afaik, view-mode only let's you react to the browser being in
>>>>>> fullscreen/chromeless mode. It doesn't let you set/request that 
>>>>>> mode.
>>>>> Yeah, I realized that after I sent my message.
>
> FWIW the viewmodes attribute of Widget Packaging and Configuration 
> allows the app author to *request* modes defined by veiw-modes, in 
> order of preference: 
> http://www.w3.org/TR/widgets/#the-viewmodes-attribute
>
>>>> The fullscreen API http://www.w3.org/TR/fullscreen/ allows 
>>>> requesting fullscreen - but no other form of chromeless.
>>> It seems like the fullscreen API is designed to allow part of a 
>>> website/app to become temporarily full screen e.g. to display a 
>>> slide show or a movie. The declarative API reinforces that feeling.
>>>
>>> Is the use cases we're interested in here (fullscreen, chromeless 
>>> apps) covered by this spec? The abstract is rather vague. ;)
>
> It allows for chromeless fullscreen, but does not support a 
> non-fullscreen chromeless app.
>
> Since "temporarily full screen" can mean "from when I launch this game 
> until three days later when I decide to stop playing and have a 
> shower", and "part of a website/app" can be "everything you see", I 
> think it meets the fullscreen use case.
>
>> No, the fullscreen API requires the transition to fullscreen mode to 
>> be user-initiated.
>
> Not quite. It says
>
> [[[
> User agents should ensure, e.g. by means of an overlay, that the end 
> user is aware something is displayed fullscreen. User agents should 
> provide a means of exiting fullscreen that always works and advertise 
> this to the user.
> ]]] (section 7)

OK. Still, none of Opera, Chrome, Firefox or Safari allow an onload 
handler to put an element or the entire document in fullscreen.
>
> I believe (but haven't checked, just going from my quite faulty 
> memory) that Mozilla's implementation allows an element to request 
> fullscreen, and effectively asks the user to confirm that choice 
> without requiring that the user made the request.
 From the Firefox console:
[11:17:19.293] Request for full-screen was denied because 
Element.mozRequestFullScreen() was not called from inside a short 
running user-generated event handler.
Received on Thursday, 24 January 2013 10:27:30 UTC

This archive was generated by hypermail 2.3.1 : Friday, 19 April 2013 17:36:47 UTC