> Not sure if WHATWG is doing anything, but in the W3C there > ishttps://dvcs.w3.org/hg/screen-orientation/raw-file/tip/Overview.html in the > Web Apps group
Actually I personally have a little more concerns on this API. First of all, some of current mobile browsers provide `orientation` as a number, whose value is among 0, 90 and -90, how would the current API conform to the new one? Secondly, I'd love to see a `orientationLocked` property to check if the orientation of page is locked, this is for several reasons: - It is better to keep unified with the fullscreen API which gives a `fullscreenEnabled` property - I'm a developer on 3rd-party script (e.g. ads), we investigated a bunch of users before and found out that once if a device locks its orientation, they have very little chance to unlock it, so we can provide more accurate and suitable content to a locked screen resolution, it would be much help if detection for whether the orientation is locked is possible. Last, How would it behave if my web app requests orientation locking but is placed in an `<iframe>` element and the parent browsing context is locked in another orientation? thanks 在 2013-4-18，上午7:03，Charles McCathie Nevile <cha...@yandex-team.ru> 写道： > Not sure if WHATWG is doing anything, but in the W3C there > ishttps://dvcs.w3.org/hg/screen-orientation/raw-file/tip/Overview.html in the > Web Apps group (by Mounir, who works on Firefox OS as a day job) > > I expect to know a bit more about the implementation status of this in about > a week, when the group has a face to face meeting.
