Pretty much the only API we could support on window.opener is postMessage().
We might want to consider exposing a separate interface from window.open() for activating an InAppBrowser that you want to do more with (e.g. listen to events, inject JS/CSS). On Tue, Jan 29, 2013 at 5:24 PM, Brian LeRoux <b...@brian.io> wrote: > Would it be possible to implement window.opener ?? > > I'm thinking no, due to the async nature of stuff, but allergic to > introducing more non-standard API surface. It might be time to start > documenting where Cordova MUST diverge so we can socialize this w/ the > various standards groups we interact with. > > On Tue, Jan 29, 2013 at 9:15 AM, Andrew Grieve <agri...@chromium.org> > wrote: > > No. > > > > We do plan to support asynchronous JS communication in the future though. > > We didn't have a bug for it, so I've now created one: > > https://issues.apache.org/jira/browse/CB-2305 > > > > On Tue, Jan 29, 2013 at 7:35 AM, Dan Mullins <dmullin...@gmail.com> > wrote: > > > >> If I open a local file in the InAppBrowser, can it communicate via > >> javascript to the main application? > >> > >> For instance, if index.html defines the global function doSomething > >> and opens local.html: > >> > >> function doSomething(input) { > >> alert('hello ' + input) > >> } > >> > >> document.addEventListener("deviceready", onDeviceReady, false); > >> > >> function onDeviceReady() { > >> iabRef = window.open('local.html', '_blank', 'location=yes'); > >> } > >> > >> Can local.html call doSomething? > >> function init() { > >> doSomething('child view'); > >> } > >> > >> I'm not having any success and want to make sure I'm not missing > something. > >> > >> Dan > >> >
