You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cordova.apache.org by "Peter (JIRA)" <ji...@apache.org> on 2013/09/11 07:50:51 UTC

[jira] [Commented] (CB-4005) InApp Browser keeps using the old prompt scripts, which don't work in InAppBrowser.

    [ https://issues.apache.org/jira/browse/CB-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764018#comment-13764018 ] 

Peter commented on CB-4005:
---------------------------

Please see CB-4788 for a potentially magical workaround
                
> InApp Browser keeps using the old prompt scripts, which don't work in InAppBrowser.
> -----------------------------------------------------------------------------------
>
>                 Key: CB-4005
>                 URL: https://issues.apache.org/jira/browse/CB-4005
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: mobile-spec
>    Affects Versions: 2.8.0
>            Reporter: Tim Kim
>            Assignee: Joe Bowser
>            Priority: Minor
>
> Related to issue: https://issues.apache.org/jira/browse/CB-3665#comment-13692456
> Steps to reproduce:
> - Go to the In App Browser manual tests
> - Under Local URL, hit any of the last three tests (eg, Target=Blank: InAppBrowser, Target=Random: InAppBrowser, Target=Random, no location bar: InAppBrowser).
> - App will launch inapp browser
> - Hit back button
> - App unresponsive (can still scroll), but can't click on any buttons
> - Logcat shows a stream of error messages: I/Web Console( 5375): processMessage failed: invalid message: at file:///android_asset/www/cordova.js:977

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira