incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shazron Abdullah (JIRA)" <>
Subject [jira] [Commented] (CB-94) OpenAllWhitelistURLsInWebView setting still problematic
Date Wed, 19 Sep 2012 23:07:08 GMT


Shazron Abdullah commented on CB-94:

Once we have InAppBrowser tasks (cross-platform) we should close this and refer to that task.
> OpenAllWhitelistURLsInWebView setting still problematic
> -------------------------------------------------------
>                 Key: CB-94
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>            Reporter: Shazron Abdullah
>            Assignee: Shazron Abdullah
>             Fix For: 2.2.0
> The good news: OpenThisWhitelistURLsInWebView works perfectly. 
> The not so good news: Once that boolean is set to yes, there is no way to force a link
to jump out and open in a browser. It's all or nothing. How, in the case of an app requiring
OpenAllWhitelistURLsInWebView = Yes for some pages, can you also force a particular link to
open outside of the in-app webview?
> In practice, it would be nice (and fairly universally useful) to be able to specify whether
a link's behavior does or does not open in webview on an individual basis. For example in
the same app you have some embed or iframe links that should be opened in the app's webview,
and, other links on a FB or twitter badge to jump out to follow or to "like" a page, or "if
you like this app, click here to jump to our website to find out more" types of links.
> Maybe it is as simple as using target="_blank" inside an < a> tag to signify jumping
out of the app and opening in a browser?
> or maybe this scheme as an expected behavior ...
> If the OpenAllWhitelistURLsInWevView boolean is set to YES,
> then,
> any external links in the whitelist (ExternalHosts array) will open up in WebView.
> Inversely,
> any external links NOT on the whitelist will open externally.
> Thoughts?

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:

View raw message