Sorry for the delay! We've had an opportunity to discuss your suggestions and comments with our internal teams and agree with your approach. The main original concerns we had were: * Creating a dependency between the screen and device orientation specs. Based on your comments this doesn't seem to be a concern. * Breaking existing implementation. Again, based on your comments this doesn't seem to be a concern.
The Z axis concerns I stated in my previous message was due to my misunderstanding of how the Z axis is mapped. Tab and Jonas, you are correct, the Z coordinate values are irrespective of how the device is being held (portrait or landscape). We should provide guidance to developers that the X and Y device orientation coordinate axis will be aligned to the current screen orientation. Also, developers should request an orientation lock to avoid the possibility of their device orientation resetting. As a next steps, who is responsible for updating the current device orientation specification? Thanks. Dhruv On Friday, August 16, 2013 10:08 AM, Tab Atkins Jr. [mailto:[email protected]] >Because that's nonsensical for landscape devices, or apps who are fine with >being rotated to landscape. It's only simpler for spec authors - it requires >>extra work for web authors. ~TJ
