Re: inAppBrowser API issue

2013-05-28 Thread Andrew Grieve
he operation. > > > > Jonathan > > > > > > -Original Message- > > From: [email protected] [mailto:[email protected]] On Behalf Of Braden > > Shepherdson > > Sent: Tuesday, May 28, 2013 11:10 AM > > To: [email protected] > > Su

Re: inAppBrowser API issue

2013-05-28 Thread Braden Shepherdson
or, it will not work if onError event handler > cannot be added before the operation. > > Jonathan > > > -Original Message- > From: [email protected] [mailto:[email protected]] On Behalf Of Braden > Shepherdson > Sent: Tuesday, May 28, 2013 11:10 AM > To: dev@cordo

RE: inAppBrowser API issue

2013-05-28 Thread Li, Jonathan
r event handler cannot be added before the operation. Jonathan -Original Message- From: [email protected] [mailto:[email protected]] On Behalf Of Braden Shepherdson Sent: Tuesday, May 28, 2013 11:10 AM To: [email protected] Subject: Re: inAppBrowser API issue If the event really

Re: inAppBrowser API issue

2013-05-28 Thread Braden Shepherdson
If the event really did fire before the event listener was added, the Javascript engine is broken. When the event is triggered (which may happen in another browser thread or something) it will be added to the event queue in the Javascript engine. That event will not be processed until the currently

inAppBrowser API issue

2013-05-28 Thread Li, Jonathan
Not sure whether this is a right place for this issue, but the javascript interface for InAppBrowser does not make much sense. The below code is from cordova document: var ref = window.open('http://apache.org', '_blank', 'location=yes'); ref.addEventListener('loadstart', function() { alert(event.u