Agree. [PROPOSAL]
1. If a URL is not in the whitelist, it will be passed to the default system browser regardless of any other rule. ( this will be handled on the native side, by the framework and the JS side may not even know it has happened. ) 2. If ChildBrowser is present, it should include code to intercept target._blank and polyfil window.open to its own API. 3. ChildBrowser should get an additional API to specifically target the system default browser. On 2012-08-06, at 3:41 PM, Shazron <[email protected]> wrote: > iOS: It can only work if window.open actually calls a native plugin > behind the scenes, and not rely on the UIWebView implementation. This > native plugin will then spawn Mobile Safari / ChildBrowser or > whatever. > > On Mon, Aug 6, 2012 at 3:36 PM, Shazron <[email protected]> wrote: >> Brian: "if we have a window.open programatic API then we can walk the DOM, >> find elements with a target=blank and use that api to call it....so it >> is possible. *shrug" >> >> It still doesn't get past the whitelist, like I explained. >> >> On Mon, Aug 6, 2012 at 3:27 PM, Brian LeRoux <[email protected]> wrote: >>>> I think the API should provide the ability to target >>>> a) the current DOM >>> >>> window.location should fit this bill >>> >>>> b) the default browser >>> >>> yes, whatever that is on the platform its got tho.... >>> >>>> c) a plugin ( child browser ) >>> >>> wait --- oh, I see what you mean, but maybe this is what WebIntents >>> and/or WebActivities are for?
