W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2014

[Bug 24609] New: Can unlockOrientation() cause an orientationchange event to be fired?

From: <bugzilla@jessica.w3.org>
Date: Mon, 10 Feb 2014 20:41:31 +0000
To: public-webapps@w3.org
Message-ID: <bug-24609-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24609

            Bug ID: 24609
           Summary: Can unlockOrientation() cause an orientationchange
                    event to be fired?
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Screen Orientation
          Assignee: mounir@lamouri.fr
          Reporter: dchris@gmail.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org

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?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 10 February 2014 20:41:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:21 UTC