incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Libby Baldwin (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CB-213) Add orientationchange event to Android
Date Tue, 07 Feb 2012 17:48:59 GMT

    [ https://issues.apache.org/jira/browse/CB-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202567#comment-13202567
] 

Libby Baldwin commented on CB-213:
----------------------------------

This is only slightly off-topic: Mentioning the existence of both difference in orientation
reporting (0, 90, ...) and bugs in screen/device values after orientationchange event in Android.

Seen:
Samsung Galaxy Tablet 10.1/3.1: Portrait == 90, -90 vs. Landscape == 1, 180

Moto. Droid/2.2.3: Portrait == 0, 180 vs. Landscape == 90, -90, EXCEPT at doc load when it
matches tablet (plus another indication of bug where width/height are changed before vs. after
orientationchange event).

Accommodating different devices after the API standard  set will probably be needed (like
the muck jQuery Mobile does to standardize portrait vs. landscape WRT orientationchange event).
                
> Add orientationchange event to Android
> --------------------------------------
>
>                 Key: CB-213
>                 URL: https://issues.apache.org/jira/browse/CB-213
>             Project: Apache Callback
>          Issue Type: New Feature
>          Components: Android
>            Reporter: Ben Plowman
>            Assignee: Joe Bowser
>            Priority: Minor
>
> On iOS currently, an "orientationchange" event is fired every time the phone rotation
changes. This event is passed an int parameter which is 0 for portrait, 90 for landscape right,
-90 for landscape left, and 180 for upside down portrait. We should match this behavior on
Android. This functionality was requested here: https://github.com/cordova/cordova-android/issues/6.
I have also seen other complaints a few other places asking for this.
> I am working on a patch for this that I need to refine and test a little bit before it
is ready to roll out.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message