You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cordova.apache.org by "Shazron Abdullah (JIRA)" <ji...@apache.org> on 2013/02/11 22:41:14 UTC

[jira] [Comment Edited] (CB-2094) Cordova 2.3.0 not reliably firing deviceready after reload of local files

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

Shazron Abdullah edited comment on CB-2094 at 2/11/13 9:39 PM:
---------------------------------------------------------------

Sorry my assumption is wrong - +new Date would not have a collision across time zones (was doing local time thinking, not UTC thinking)
                
      was (Author: shazron):
    Sorry my assumption is wrong - +new Date would not change across time zones.
                  
> Cordova 2.3.0 not reliably firing deviceready after reload of local files
> -------------------------------------------------------------------------
>
>                 Key: CB-2094
>                 URL: https://issues.apache.org/jira/browse/CB-2094
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CordovaJS, iOS
>    Affects Versions: 2.3.0
>            Reporter: Bob Moore
>            Assignee: Andrew Grieve
>              Labels: Cordova, deviceready, iOS6
>             Fix For: 2.4.0
>
>         Attachments: index.html, MainViewController.h, MainViewController.m, MainViewController.xib
>
>
> I've added a semi transparent home button to the MainViewController which loads the local index.html file within my Cordova 2.30 project. After I've moved on to a remote page, (may be Cordova enabled, may not) and I return with the home button, sometimes deviceready does not fire. It may fire a few times then stop. Once it stops the only way to fix the issue is to send the app to the background (deviceready will now fire) and return.
> This same technique works fine in Cordova 2.20

--
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