- From: Lars Erik Bolstad <lbolstad@opera.com>
- Date: Thu, 24 Jan 2013 10:28:13 +0100
- To: Tobie Langel <tobie@fb.com>
- CC: Charles McCathie Nevile <chaals@yandex-team.ru>, Dominique Hazael-Massieux <dom@w3.org>, Jo Rabin <jo@linguafranca.org>, "public-coremob@w3.org" <public-coremob@w3.org>
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. >> 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. ;) > > Thanks, > > --tobie No, the fullscreen API requires the transition to fullscreen mode to be user-initiated. Lars Erik
Received on Thursday, 24 January 2013 09:28:58 UTC