[
https://issues.apache.org/jira/browse/CB-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kuan Yi Ming updated CB-3809:
-----------------------------
Description:
If jQuery Mobile is in use in a PG app, the body onload function triggers after
the initial deviceready + initial online/offline event in version 2.7.0.
Thus, the Javascript code samples at
http://docs.phonegap.com/en/2.7.0/cordova_events_events.md.html#Events simply
won't run the deviceready event, as well as the initial online or offline event
when the app is launched if jQM is used.
The code works in 2.6.0 and earlier versions, and on iOS. Android on 2.8.1
however still has the same issue.
was:
If jQuery Mobile is in use in a PG app, the body onload function triggers after
the initial deviceready + initial online/offline event in version 2.7.0.
Thus, the Javascript code samples at
http://docs.phonegap.com/en/2.7.0/cordova_events_events.md.html#Events simply
won't run the deviceready event, as well as the initial online or offline event
when the app is launched if jQM is used.
The code works in 2.6.0 and earlier versions, and on iOS. 2.8.1 however still
has the same issue.
> Online/offline/deviceready events trigger too quickly with jQuery Mobile
> ------------------------------------------------------------------------
>
> Key: CB-3809
> URL: https://issues.apache.org/jira/browse/CB-3809
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: 2.7.0, 2.8.0
> Reporter: Kuan Yi Ming
> Assignee: Joe Bowser
>
> If jQuery Mobile is in use in a PG app, the body onload function triggers
> after the initial deviceready + initial online/offline event in version
> 2.7.0.
> Thus, the Javascript code samples at
> http://docs.phonegap.com/en/2.7.0/cordova_events_events.md.html#Events simply
> won't run the deviceready event, as well as the initial online or offline
> event when the app is launched if jQM is used.
> The code works in 2.6.0 and earlier versions, and on iOS. Android on 2.8.1
> however still has the same issue.
--
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
