- From: Mounir Lamouri <mounir@lamouri.fr>
- Date: Thu, 08 Nov 2012 14:57:41 +0000
- To: www-style@w3.org
Hi, In the WebApps WG, we are trying to work on an API that would allow reading, and locking the screen orientation from script. See: http://dvcs.w3.org/hg/screen-orientation/raw-file/tip/Overview.html The use cases we wanted to solve with that API required us to be able to lock on a specific orientation (for example games) so we had to define more orientation values like 'portrait-primary', 'portrait-secondary', 'landscape-primary' and 'landscape-secondary'. Those values allow a better granularity for the orientation locking but also allow reading the exact current orientation. So, actually, I wonder if the CSS Device Adaptation would still be interested in keeping the 'orientation' property even if there is now an API that allows to do more. I'm not certain there is a huge use case for declarative orientation lock other than for web apps but that should happen in the manifest format. I am not trying to push to remove this feature, just asking. Also, given that Screen Orientation API defines a larger set of values, would the CSS Device Adaptation specification be interested in using those for the 'orientation' property? Cheers, -- Mounir
Received on Thursday, 8 November 2012 14:58:04 UTC