Re: Global Javascript in InAppBrowser

2013-01-30 Thread Shazron
Another request (on my blog post comments) is for the InAppBrowser to *follow* the whitelist: http://shazronatadobe.wordpress.com/2012/12/10/whats-new-in-cordova-ios-2-3-0/#comment-4706 On Tue, Jan 29, 2013 at 2:40 PM, Andrew Grieve wrote: > Pretty much the only API we could support on window.o

Re: Global Javascript in InAppBrowser

2013-01-30 Thread Filip Maj
Is there any way we can formalize this behavior in a native (or native + JS) test (for any platform)? On 1/30/13 10:11 AM, "Shazron" wrote: >"Right now it seems every call to window.open is going to give you a new >instance" --> on iOS it is re-used. > >I suppose we could handle those implied ha

Re: Global Javascript in InAppBrowser

2013-01-30 Thread Shazron
"Right now it seems every call to window.open is going to give you a new instance" --> on iOS it is re-used. I suppose we could handle those implied handlers, those are just JavaScript changes I believe On Tue, Jan 29, 2013 at 10:40 PM, Jesse wrote: > The original interface was simply to allow

Re: Global Javascript in InAppBrowser

2013-01-29 Thread Jesse
The original interface was simply to allow the host code to monitor location changes. This allows for oauth workflows. Data can(?) be passed back and forth via a query string param *afaik*. Supporting window.opener is full of blockers, not just async issues, but also security. I think the inappbr

Re: Global Javascript in InAppBrowser

2013-01-29 Thread Andrew Grieve
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 LeRo

Re: Global Javascript in InAppBrowser

2013-01-29 Thread Brian LeRoux
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 wit

Re: Global Javascript in InAppBrowser

2013-01-29 Thread Andrew Grieve
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 wrote: > If I open a local file in the InAppBrowser, can it communicate