This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24698 - Expose/lock to the screen orientation angle
Summary: Expose/lock to the screen orientation angle
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Screen Orientation (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Mounir Lamouri
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-17 16:25 UTC by Mounir Lamouri
Modified: 2014-04-03 21:10 UTC (History)
3 users (show)

See Also:

Attachments

Description Mounir Lamouri 2014-02-17 16:25:06 UTC 
The API exposes only the screen orientation name but not the actual angle compared to the device natural orientation. Knowing that can be useful for different reasons. For example, in combination with the device orientation events, it would make possible to write a reliable compass app.

The details are not yet clear but we might want to expose 0/90/180/270 in something like screen.orientationAngle and maybe allow lockOrientation() to take those values too.
Comment 1 Mounir Lamouri 2014-04-03 21:10:40 UTC 
The exact change is:
https://dvcs.w3.org/hg/screen-orientation/rev/d42347e9ab3d

But simpler to look at the current specification.