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

[Bug 24610] New: What happens when unlockOrientation() is called but no orientation is locked?

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

            Bug ID: 24610
           Summary: What happens when unlockOrientation() is called but no
                    orientation is locked?
           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

What happens when unlockOrientation() is called but no orientation is locked?
The specification does not clearly mention this case, I assume we should return
early (silently).

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

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