cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jcesarmobile (JIRA)" <>
Subject [jira] [Commented] (CB-10778) Documentation inaccurate
Date Thu, 10 Mar 2016 11:55:40 GMT


jcesarmobile commented on CB-10778:

On the first issue, I think it refers to the regular, not the inAppBrowser one.
In fact, according to the currect docs, you should use instead of

On the issue 2, I agree, in fact, in my tests, it doesn't apply to iframes on android, just
the opposite of what the docs say. I don't have an allow-navigation tag and I can see the
iframe content.
On iOS I can't see without the allow-navigation tag

> Documentation inaccurate
> ------------------------
>                 Key: CB-10778
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: Docs, Plugin Whitelist
>         Environment: Cordova for Android 5.1.1
>            Reporter: Jacob Weber
>            Priority: Minor
> h3. Issue 1:
> states:
> "Intent Whitelist ... does not apply to plugins, only hyperlinks and calls to"
> At least on Android, <allow-intent> doesn't seem to affect calls when
InAppBrowser is installed. For example, this doesn't use the whitelist:
> {code}
>'market://details?', '_system');
> {code}
> but this does:
> {code}
> window.location = 'market://details?';
> {code}
> h3. Issue 2:
> states:
> "Navigation Whitelist...controls which URLs the WebView itself can be navigated to. Applies
to top-level navigations only. Quirks: on Android it also applies to iframes for non-http(s)
> On iOS, this seems to apply to iframes as well. If I insert an iframe into the top-level
page, it won't be loaded without an <allow-navigation> entry for the iframe's src.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message