Inconsistent behavior when opening inappbrowser window

["Li, Jonathan" <jo...@sap.com>]

When creating inappBrowser in cordova app, for iOS, only a single
uiwebview instance is created for multiple window.open method calls, and
it only shows the content of last window.open's url content. However, on
Android client, each window.open method call will create a separate
webview instance with its own url content.
 
Just want to confirm is this an expected behavior? Is there any change
planned to make the behavior more consistent across all client platforms?

Sample code to call window.open multiple times:
var windowRef = window.open( 'http://google.com', '_blank',
'location=yes');
var windowRef2 = window.open('http://apache.org', '_blank',
'location=yes');


Regards
Jonathan

Re: Inconsistent behavior when opening inappbrowser window

[Andrew Grieve <ag...@chromium.org>]

It's certainly not ideal. It would be better for this to be consistent.
That said, probably low priority to fix (pull requests welcome). Could
maybe even fix it on the JS side (existing.close() before open() next)


On Wed, Jul 2, 2014 at 3:20 PM, Li, Jonathan <jo...@sap.com> wrote:

>
> When creating inappBrowser in cordova app, for iOS, only a single
> uiwebview instance is created for multiple window.open method calls, and
> it only shows the content of last window.open's url content. However, on
> Android client, each window.open method call will create a separate
> webview instance with its own url content.
>
> Just want to confirm is this an expected behavior? Is there any change
> planned to make the behavior more consistent across all client platforms?
>
> Sample code to call window.open multiple times:
> var windowRef = window.open( 'http://google.com', '_blank',
> 'location=yes');
> var windowRef2 = window.open('http://apache.org', '_blank',
> 'location=yes');
>
>
> Regards
> Jonathan
>
>