Return-Path: X-Original-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 215C8D5BB for ; Sat, 22 Sep 2012 23:09:08 +0000 (UTC) Received: (qmail 20163 invoked by uid 500); 22 Sep 2012 23:09:07 -0000 Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org Received: (qmail 20137 invoked by uid 500); 22 Sep 2012 23:09:07 -0000 Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: callback-dev@incubator.apache.org Delivered-To: mailing list callback-dev@incubator.apache.org Received: (qmail 20129 invoked by uid 99); 22 Sep 2012 23:09:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Sep 2012 23:09:07 +0000 Date: Sun, 23 Sep 2012 10:09:07 +1100 (NCT) From: "Dominic N. Sotirescu (JIRA)" To: callback-dev@incubator.apache.org Message-ID: <1958413613.112743.1348355347853.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (CB-1527) onorientationchange event not fired in iOS6 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Dominic N. Sotirescu created CB-1527: ---------------------------------------- Summary: onorientationchange event not fired in iOS6 Key: CB-1527 URL: https://issues.apache.org/jira/browse/CB-1527 Project: Apache Cordova Issue Type: Bug Components: iOS Affects Versions: 2.0.0 Environment: Building on Mac Air with Mountain Lion. Xcode 4.5. iOS6 on mobile device (iPhone4, iPad3) Reporter: Dominic N. Sotirescu Assignee: Shazron Abdullah Fix For: 2.1.0 As soon as I upgraded to iOS6 and re-built/deployed the app, onorientationchange doesn't fire anymore. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira