Skip to content
This repository

Enable whitelisting support for embedded content #118

Open
nukulb opened this Issue · 4 comments

3 participants

Nukul Bhasin Ken Wallis Jeffrey Heifetz
Nukul Bhasin
nukulb commented

All api's are available to embedded content, regardless of config.xml

App is a local index.html with app api's whitelisted, embedded iframe
with no api's allowed (think of an rss reader app)

The embedded content has access to any api the app has.

Expected:
@kwallis - fill in the details on what you want the behavior to be for remote url vs. local url

Ken Wallis
Owner
Nukul Bhasin
nukulb commented

different domains is a better question.

Here is the problem, there is no way to find out from that if a NetworkResourceRequest came from an iFrame or original page. So I will be opening a PR.

Ken Wallis
Owner

Fixed?

cc @jeffheifetz

Jeffrey Heifetz

Not yet

Stephan Leroux sleroux referenced this issue from a commit
Commit has since been removed from the repository and is no longer available.
Stephan Leroux sleroux referenced this issue from a commit
Commit has since been removed from the repository and is no longer available.
Stephan Leroux sleroux referenced this issue from a commit
Commit has since been removed from the repository and is no longer available.
Stephan Leroux sleroux referenced this issue from a commit
Commit has since been removed from the repository and is no longer available.
Stephan Leroux sleroux referenced this issue from a commit in blackberry-webworks/BB10-WebWorks-Framework
Stephan Leroux Fixes blackberry/BB10-WebWorks-Framework#118
Changes a webview's requests to use the referrer from the
NetworkResourceRequestedEvent instead of originalLocation.

Reviewed By: Jeffrey Heifetz <jheifetz@rim.com>
Tested By: Igor Shneur <ishneur@rim.com>
2aeffdf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.