cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Monroy (JIRA)" <>
Subject [jira] [Commented] (CB-9845) inappbrowser close function not working as intended, leaving instance of inappbrowser running
Date Mon, 26 Oct 2015 03:43:27 GMT


Jesse Monroy commented on CB-9845:

Using a programming interface in an undocumented manner is not a bug. In some parts of the
world it is called an "undocumented feature". 

If you use the programming interface - as it is designed, then you will not have the problem
you are describing.

Please read the documentation to resolve your issue.

> inappbrowser close function not working as intended, leaving instance of inappbrowser
> ---------------------------------------------------------------------------------------------
>                 Key: CB-9845
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Plugin InAppBrowser
>    Affects Versions: Master
>         Environment: Mac OSX/Win10/Ubuntu14.04
>            Reporter: Sebastian Betzinger
>            Priority: Critical
>              Labels: 1.0.1, Android, inappbrowser, ios
> recent cordova tools 5.3.3, recent inappbrowser 1.0.1
> Code to reproduce:
> var ref;
> function xy() {
> ref =;
> }
> function ab() {
> ref.close();
> xy();
> }
> xy();
> ab();
> First InAppBrowser instance stays opened with url "about:blank" in foreground and a second
instance of InAppBrowser is launched in background with actual content. Using show() function
on second instance does not bring second inappbrowser to foreground, so every newly launched
instance is stuck in background.
> Should be: instance of InAppBrowser should be purged and closed instead of being held
with "about:blank"
> Also using the Toolbar/Locationbar to close the inappbrowser leaves the instance on device.
This is a matter in lack of performance regarding long time running of the apps.
line 377 dismiss seems not to work!
> workaround: direclty after a instance of IAB is closed you are not able to open another
instance of IAB except you add a setTimeout of at least 1000ms - this brings at least the
second instance into foreground.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message