This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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?
https://dvcs.w3.org/hg/screen-orientation/rev/db6f46ecb3c6