Menu
In the example app cordova provides through cordova create ..., the following code listens to the deviceready event:
bindEvents: function() {
document.addEventListener('deviceready', this.onDeviceReady, false);
},
This is nice, but what happens when the event is fired before I've had time to listen for it? As an example, replace the code from the example app (above) with the following:
bindEvents: function() {
setTimeout(function () {
document.addEventListener('deviceready', this.onDeviceReady, false);
}, 2000)
},
In this example, this.onDeviceReady is never called. Would there not be a better, more reliable way to check if cordova is ready? Something like this:
bindEvents: function() {
setTimeout(function () {
if (window.cordovaIsReady) {
this.onDeviceReady()
} else {
document.addEventListener('deviceready', this.onDeviceReady, false);
}
}, 2000)
},
896
As per the cordova documentation
The deviceready event behaves somewhat differently from others. Any event handler registered after the deviceready event fires has its callback function called immediately.
As you can see if any event Handler is attached AFTER the deviceready has fired it will be called immediately.
In a setTimeout function this is a no longer pointing to the intended object, the context is different. Therefore your handler will never be called.
You can try the below code by placing it in your <head> tag, where I am using global functions/variables (avoiding the this context issues for sake of simplicity). This should show you an alert.
<script>
function onDeviceReady () {
alert("Calling onDeviceReady()");
}
setTimeout(function () {
document.addEventListener('deviceready', onDeviceReady, false);
}, 9000);
</script>
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
