eh shax, other thread pls, also rather than making assumptions on understanding pls explain yourself. I know its been beat to death.
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 On Mon, Aug 6, 2012 at 3:20 PM, Shazron <[email protected]> wrote: > I think you still don't understand how the iOS whitelist works, you > have to really understand how it works - please (it is not just that > handler). It IS impossible. The whitelist will reject it, no matter > what happens in that handler. We are talking about URLs NOT in the > whitelist. > > On Mon, Aug 6, 2012 at 3:11 PM, Brian LeRoux <[email protected]> wrote: >> lets start a new thread. randy mcmillen had a pull req that worked >> (for me) on ios so not impossible. also, if we had a programmic api >> then pure js polyfill obv also 'possible'. >> >> On Mon, Aug 6, 2012 at 3:01 PM, Shazron <[email protected]> wrote: >>> Well whomever starts it -- window.open, sure, that can work. >>> target=_blank, 100% no for iOS, it is impossible (yes, really) for the >>> thousandth time - read CB-362. I fear it will be a rehash of that mega >>> thread again... why are we discussing this again? >>> >>> On Mon, Aug 6, 2012 at 2:53 PM, Brian LeRoux <[email protected]> wrote: >>>> start it? =) >>>> >>>> On Mon, Aug 6, 2012 at 2:45 PM, Jesse MacFadyen <[email protected]> >>>> wrote: >>>>> How do I reply to the separate thread? >>>>> >>>>> Cheers, >>>>> Jesse >>>>> >>>>> Sent from my iPhone5 >>>>> >>>>> On 2012-08-06, at 2:36 PM, Brian LeRoux <[email protected]> wrote: >>>>> >>>>>> I think we should back off on new APIs until plugin tooling (discovery >>>>>> esp) is solid (so we can install/remove). We def want to make it a >>>>>> supported API but probably do not want to roll new code into >>>>>> platforms. >>>>>> >>>>>> SEPARATE THREAD: The API for childbrowser should be window.open w/ a >>>>>> polyfill for target=blank to be in harmony w/ browsers and our goal of >>>>>> compatibility/obsolescence. >>>>>> >>>>>> >>>>>> On Mon, Aug 6, 2012 at 2:22 PM, Shazron <[email protected]> wrote: >>>>>>> We've had a lengthy discussion about this (search the archives). >>>>>>> Consensus was to use ChildBrowser as a core plugin. When can this be >>>>>>> scheduled for all platforms? >>>>>>> >>>>>>> https://issues.apache.org/jira/browse/CB-362 >>>>>>> https://twitter.com/CNG/statuses/232531840534192128
