[
https://issues.apache.org/jira/browse/CB-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205842#comment-13205842
]
Joe Bowser commented on CB-132:
-------------------------------
OK, here's where we're at with this:
Currently we override the URL loading for file://, this means that we load the
file:// using a custom method instead of just letting the WebView do its job.
However, the current way PhoneGap works breaks when we let WebView do its job
of handling iFrames. This should be fixed with CB-190 where we let the
application do its job on the history, but this still has to be tested.
Tip: If something is broken in both Android 2.3 and Android 4.0, it's more
likely our fault because we had to write a work-around of some kind.
> Loading a local file into an iframe opens in the main app window instead
> ------------------------------------------------------------------------
>
> Key: CB-132
> URL: https://issues.apache.org/jira/browse/CB-132
> Project: Apache Callback
> Issue Type: Bug
> Components: Android
> Affects Versions: 1.2.0
> Environment: Tested on Android 2.3.6, Android 4.0.2; tested with
> PhoneGap 1.2.0 and a locally built 1.3.0.
> Reporter: Brion Vibber
> Assignee: Joe Bowser
> Labels: iframe
> Fix For: 2.0.0
>
>
> Test program: https://github.com/brion/iframe-android-test
> Loading the local file 'empty.html' (second button) in the iframe opens it in
> the main application window instead. This destroys whatever UI and logic were
> living in the main window.
> iframe source is being set by setting the 'src' property on the element's DOM
> node.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
