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 24609 - Can unlockOrientation() cause an orientationchange event to be fired?
Summary: Can unlockOrientation() cause an orientationchange event to be fired?
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Screen Orientation (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Mounir Lamouri
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-10 20:41 UTC by Chris Dumez
Modified: 2014-02-17 15:12 UTC (History)
2 users (show)

See Also:

Attachments

Description Chris Dumez 2014-02-10 20:41:31 UTC 
The specification is currently clear about the fact that calling lockOrientation() can cause an orientationchange event to be fired if the screen orientation had to be changed to meet the locking requirements.

However, the specification is not as clear about unlockOrientation() IMHO. When calling unlockOrientation(), a new screen orientation may be used to best match the current device orientation, and thus an orientationchange event may be fired.

Maybe this should be clarified in the specification?