The InAppBrowser instance does not automatically dispatch the events after the system browser is opened via InAppBrowser. Please follow the generic code below:
The _inAppBrowser instance works fine for the first time. But as soon as the system browser is opened, the event 'for eg. loadstop' does not fire automatically. This bug/issue appears only when system browser is open. for eg, the following code works perfectly.
It seems the new '_inAppBrowserSystem' instance somehow interrupts the event dispatcher for the '_inAppBrowser' instance. I found that if the _inAppBrowserSystem is assign the same eventHandler, then _inAppBrowser starts to dispatch the event. The following code helped me solve the problem but this should still be registered as a bug.
I have the solution for now, but I still register this as a bug as the event dispatcher is not consistent. For instance, the code in 'example 1' should work as in 'example 2'. If there is not a quick fix, I hope at least the documentation get updated with this hack.