[jira] [Comment Edited] (CB-4005) InApp Browser continuously throws errors on Android

["Joe Bowser (JIRA)" <ji...@apache.org>]

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

Joe Bowser edited comment on CB-4005 at 6/28/13 9:54 PM:
---------------------------------------------------------

This bug is caused by Cordova trying to create infinite prompts on a standard browser.  This will then cripple the application and cause it to crash.  You can pretty much crash any browser by doing something like this:

{code}
while(1) { alert("Only idiots make infinite loops!!"); }
{code}

Now, the solution to this would be launching InAppBrowser as a separate intent and having it send back the info, but then it would be subject to the same issues as the Camera Plugin.  Honestly, there are very few real use cases to use the InAppBrowser (such as third-party authentication) that people should be offloading to a real Web Browser designed for the web for curation of web content.

This is the danger of letting your plugins mess around with your application's UI thread, it will eventually screw it over if someone does something like this.
                
      was (Author: bowserj):
    This bug is caused by Cordova trying to create infinite prompts on a standard browser.  This will then cripple the application and cause it to crash.  You can pretty much crash any browser by doing something like this:

{{code}}
while(1) { alert("Only idiots make infinite loops!!"); }
{{code}}

Now, the solution to this would be launching InAppBrowser as a separate intent and having it send back the info, but then it would be subject to the same issues as the Camera Plugin.  Honestly, there are very few real use cases to use the InAppBrowser (such as third-party authentication) that people should be offloading to a real Web Browser designed for the web for curation of web content.

This is the danger of letting your plugins mess around with your application's UI thread, it will eventually screw it over if someone does something like this.
                  
> InApp Browser continuously throws errors on Android
> ---------------------------------------------------
>
>                 Key: CB-4005
>                 URL: https://issues.apache.org/jira/browse/CB-4005
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 2.8.0
>            Reporter: Tim Kim
>            Assignee: Joe Bowser
>            Priority: Minor
>             Fix For: 3.0.0
>
>
> 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