[
https://issues.apache.org/jira/browse/CB-6230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051608#comment-14051608
]
Jacob Weber commented on CB-6230:
---------------------------------
[~edewit] I tried that exact listener, but the "exit" even never gets fired.
Also, when I'm seeing this problem in real life, it's not due to the async
nature of the close() call. I'm calling close() several minutes before I try to
call window.open() again.
> InAppBrowser closes after opening, instead of before
> ----------------------------------------------------
>
> Key: CB-6230
> URL: https://issues.apache.org/jira/browse/CB-6230
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Plugin InAppBrowser
> Affects Versions: 3.4.0, 3.5.0
> Reporter: Jacob Weber
>
> In Cordova 3.4, with InAppBrowser 0.3.3, create a new project using the CLI.
> In www/js/index.js, make the following change:
> {noformat}
> onDeviceReady: function() {
> app.receivedEvent('deviceready');
> document.addEventListener('click', function() {
> if (window.myWindow) window.myWindow.close();
> window.myWindow = window.open('http://www.google.com', "_blank");
> });
> },
> {noformat}
> Tap the page once, and a browser will appear. Close the browser. Then tap the
> app again. This time the browser will appear for a split second, then close
> right away. The close() call seems to be happening after the subsequent
> open() call, instead of before it.
> This was working in 3.3, with InAppBrowser 0.2.5.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
