- From: Bruno Racineux <bruno@hexanet.net>
- Date: Thu, 13 Mar 2014 23:51:24 -0700
- To: Mounir Lamouri <mounir@lamouri.fr>, public-webapps <public-webapps@w3.org>
- CC: Jonas Sicking <jonas@sicking.cc>, Anne van Kesteren <annevk@annevk.nl>
On 3/13/14 10:59 AM, "Mounir Lamouri" <mounir@lamouri.fr> wrote: >I recently landed a usage counter for window.orientation. It will take >some time to roll to Chrome Android stable but hopefully we will find >out if window.orientation is actually used a lot. If that's the case and >other UA want to implement it, we could incorporate that into this >specification. In any case, I would like to add this feature but not as >|window.orientation|. > > >Your use case will be taken care of, see this bug: >https://www.w3.org/Bugs/Public/show_bug.cgi?id=24698 You could alternatively just have a 'natural' orientation boolean flag, to help assessing the angle at the initial rotation level (without having to first rotate to find out). The flag would also add the ability to lock to the "natural" orientation. My main rebuttal of the orientation values is not the lack of angle, but rather the lack of instant identification of this 'natural' orientation state. We can figure out the mapping to angles with such a flag. So should it a better or easier implementation option, perhaps avoiding redundancy, that would work too, and the only thing needed to address my case.
Received on Friday, 14 March 2014 06:51:54 UTC