You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/06/05 17:28:22 UTC

[jira] [Commented] (CB-3420) InAppBrowser Option to Start Hidden

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

ASF subversion and git services commented on CB-3420:
-----------------------------------------------------

Commit dcbd189803681d61d261f4a5f76cd89a41b605ae in branch refs/heads/master from [~david.kemp@melbourneit.com.au]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-js.git;h=dcbd189 ]

CB-3420: add hidden option to InAppBrowser

                
> InAppBrowser Option to Start Hidden
> -----------------------------------
>
>                 Key: CB-3420
>                 URL: https://issues.apache.org/jira/browse/CB-3420
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: CordovaJS, mobile-spec
>            Reporter: Andrew Grieve
>            Assignee: David Kemp
>            Priority: Minor
>
> 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