[
https://issues.apache.org/jira/browse/CB-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694358#comment-13694358
]
Shazron Abdullah commented on CB-3420:
--------------------------------------
It's implemented in Android too. We already had this discussion in the ML that
"feature parity" / waiting for all platforms shouldn't prevent us from
implementing it for the core platforms. I'll try to dig up the link to that
discussion.
> InAppBrowser Option to Start Hidden
> -----------------------------------
>
> Key: CB-3420
> URL: https://issues.apache.org/jira/browse/CB-3420
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Android, BlackBerry, CordovaJS, iOS, mobile-spec, WP7,
> WP8
> Reporter: Andrew Grieve
> Assignee: David Kemp
> Priority: Minor
> Fix For: 3.1.0
>
>
> One common use-case for the InAppBrowser is to handle an OAuth flow. Some
> flows can be done without any user interaction, so it would be great if the
> InAppBrowser had an option where it would start hidden, and could later be
> reveals through a JS call.
> E.g.
> var iab = window.open('$OAUTH_URL', 'hidden=yes');
> //some time later.
> iab.show();
--
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
