- From: Mounir Lamouri <mounir@lamouri.fr>
- Date: Thu, 04 Jul 2013 15:20:20 +0100
- To: Tobie Langel <tobie@w3.org>
- CC: public-webapps@w3.org, David Bruant <bruant.d@gmail.com>
On 24/04/13 11:13, Tobie Langel wrote: > While some of the original use cases required dynamically modifying orientation lock (e.g. the Game within a game experience[5]), key use cases simply require a declarative, page-wide setting, as described by David Bruant on the WHAT WG mailing list[6]. Hi Tobie, (First, I am so sorry for the huge delay...) I think we should not use CSS Device Adaptation to set the orientation. I am actually not sure how well CSS would handle media queries to have rules based on the orientation and setting the orientation from CSS. Wouldn't we risk to end up in an infinite loop? This one of the reasons why, for form controls, we ended up with specifying the orientation on the attribute instead of doing that in CSS. In addition, with the current work of having manifest files applying to regular web pages [1], we can hope that web pages that want to have a specific orientation could simply use a manifest file. I think using a manifest could be a good solution for that kind of use cases [2]. This said, how do you expect the orientation to work when set declaratively? Should the declaration be set as soon as authorised (on Firefox Android, that means being fullscreen [3])? It might provide an odd user experience. An alternative would be to only fulfil the declarative orientation if the page is allowed to set it at load time. [1] http://lists.w3.org/Archives/Public/public-webapps/2013AprJun/0639.html [2] http://mounir.lamouri.fr/2013/05/the-web-manifest.html Thanks, -- Mounir
Received on Thursday, 4 July 2013 14:20:47 UTC