Mailing-List: contact issues-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 22 Jan 2016 09:31:39 +0000 (UTC)
From: "Sergey Grebnov (JIRA)" <jira@apache.org>
To: issues@cordova.apache.org
Message-ID: <JIRA.12907138.1445531581000.179754.1453455099912@Atlassian.JIRA>
In-Reply-To: <JIRA.12907138.1445531581000@Atlassian.JIRA>
References: <JIRA.12907138.1445531581000@Atlassian.JIRA>
 <JIRA.12907138.1445531581694@arcas>
Subject: [jira] [Updated] (CB-9845) inappbrowser close function not working
 as intended, leaving instance of inappbrowser running
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CB-9845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Grebnov updated CB-9845:
-------------------------------
    Assignee:     (was: Sergey Grebnov)

> inappbrowser close function not working as intended, leaving instance of inappbrowser running
> ---------------------------------------------------------------------------------------------
>
>                 Key: CB-9845
>                 URL: https://issues.apache.org/jira/browse/CB-9845
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Plugin InAppBrowser
>    Affects Versions: Master
>         Environment: Mac OSX/Win10/Ubuntu14.04
>            Reporter: Sebastian Betzinger
>            Priority: Trivial
>              Labels: 1.0.1, Android, Triaged, inappbrowser, ios
>
> recent cordova tools 5.3.3, recent inappbrowser 1.0.1
> Code to reproduce:
> var ref;
> function xy() {
> ref = cordova.InAppBrowser.open(...);
> }
> 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.
> https://github.com/apache/cordova-plugin-inappbrowser/blob/master/src/android/InAppBrowser.java 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
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org