- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Mon, 2 Dec 2013 14:51:05 +0000
- To: Mounir Lamouri <mounir@lamouri.fr>
- CC: Marcos Caceres <w3c@marcosc.com>, Kenneth Rohde Christiansen <kenneth.christiansen@gmail.com>, public-webapps <public-webapps@w3.org>
On 26 Nov 2013, at 18:49, Mounir Lamouri <mounir@lamouri.fr> wrote: [...] > If 'current' is added, I wouldn't say that there is a race condition > issue because if you lock to 'current' you do not really care about the > actual orientation. > > This said, I do not think that 'current' is very useful from the JS API, > it only saves a few characters. I tend to agree. For the API that would be just syntactic sugar. OTOH for the declarative manifest [1] that would be required — assuming there’s consensus the ‘lock to current orientation' UC should be addressed, and that the API and the manifest should share the same ‘allowed orientations’ string constants, defined in [2]. Given the data we gathered on 300 apps' orientation behaviour [3], it seems the UC is not that strong. Only the iOS task switcher behaves in such a way and with no obvious reason. It seems that for this advanced use case, developers should just use the API and query its .orientation property as Mounir hinted. -Anssi [1] http://www.w3.org/2008/webapps/manifest/#orientation-member [2] https://dvcs.w3.org/hg/screen-orientation/raw-file/tip/Overview.html#allowed-orientations [3] https://docs.google.com/spreadsheet/ccc?key=0Akv8gJijerFUdFQ4RVNibXNUNElWZU05THJ4NE9BSVE
Received on Monday, 2 December 2013 14:51:40 UTC