[ https://issues.apache.org/jira/browse/CB-5126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799149#comment-13799149 ]
Clayton Grassick commented on CB-5126: -------------------------------------- Adding cordova.fireDocumentEvent("DOMContentLoaded") after the condova.js script is loaded solves the problem, but is obviously not ideal. > Android Nexus One DOMContentLoaded bug > -------------------------------------- > > Key: CB-5126 > URL: https://issues.apache.org/jira/browse/CB-5126 > Project: Apache Cordova > Issue Type: Bug > Components: Android > Affects Versions: 3.0.0 > Environment: Android Nexus One (2.3.6), Cordova 3.0.0 > Reporter: Clayton Grassick > > When loading a second page on Nexus One, cordova.js fails to fire > deviceReady. This is because after DOMContentLoaded is fired on this > particular browser, the document readyState is sometimes "loaded", not > "interactive" as it should be. The code in cordova.js that manually fires the > DOMContentLoaded checks for readyState of "interactive" or "complete", > however the document reports it as "loaded". > Other people have reported this behavior in 2.3.5: > http://stackoverflow.com/questions/13346746/document-readystate-on-domcontentloaded > (response to official answer) > I am loading cordova.js via an inserted script tag in the head, but that is > unfortunately necessary to allow auto-downloaded updates of the app. This > approach works on all other browsers that I've tested on. -- This message was sent by Atlassian JIRA (v6.1#6144)