[
https://issues.apache.org/jira/browse/CB-7758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200888#comment-14200888
]
ASF subversion and git services commented on CB-7758:
-----------------------------------------------------
Commit fc63f66e8970ab537dda1397a6b58e6d61252c17 in cordova-android's branch
refs/heads/4.0.x from [~iclelland]
[ https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=fc63f66 ]
CB-7758: Allow content-url-hosted pages to access the bridge
This allows e.g. jsHybugger to create pages with access to Cordova APIs.
We restrict access to content provider URLs which are at subdomains of the
application itself, ie, begin with "content://com.your.package.id."
> Support for content:// URIs
> ---------------------------
>
> Key: CB-7758
> URL: https://issues.apache.org/jira/browse/CB-7758
> Project: Apache Cordova
> Issue Type: New Feature
> Components: Android
> Affects Versions: 3.6.0
> Environment: Android 4.3
> Reporter: Wolfgang Flohr-Hochbichler
> Assignee: Ian Clelland
> Priority: Minor
>
> Device ready event is not fired if page is loaded via content:// protocol.
> I assume it has something to do with a security check done within
> CordovaBridge.java which triggers the following gap_init error message.
> 10-09 10:10:18.071 16719 16719 E CordovaBridge: gap_init called from
> restricted origin:
> content://com.ionicframework.ionicapp795549.jsHybugger/file:///android_asset/www/index.html#/tab/dash
> 10-09 10:10:23.075 16719 16719 D CordovaLog:
> content://com.ionicframework.ionicapp795549.jsHybugger/jshybugger.js: Line
> 112 : deviceready has not fired after 5 seconds.
> 10-09 10:10:23.075 16719 16719 I Web Console: deviceready has not fired after
> 5 seconds. at
> content://com.ionicframework.ionicapp795549.jsHybugger/jshybugger.js:112
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org
