When JIRA is back up (it's under maintenance right now), see my first/second comment on this issue: https://issues.apache.org/jira/browse/CB-362
It's a bit too long to rehash :) On Sat, May 19, 2012 at 8:17 AM, Brian LeRoux <b...@brian.io> wrote: > Sorry shaz, I must be dense but I missed the technical reasons? > On May 19, 2012 11:48 AM, "Shazron" <shaz...@gmail.com> wrote: > >> > The method I'm proposing >> > assumes all link events are trapped, inspected for a url param, and in >> > its absence, falls back to default behavior. Maybe thats not >> > realistic. Seems like both iOS and Android do not trap the target >> > attribute. Which means we'd need to add a url param so that trap is >> > caught. >> > >> >> It is not entirely a question of "nastiness" in adding a url param >> with regards to why it won't work in iOS (although imo I don't like >> it) - I have already presented valid technical reasons. >> >> With respect to achieving all our goals - not introducing a new API, >> and fixing this bug that sorely needs fixing - ChildBrowser like you >> proposed is the better bet then. So what should be the plan for this? >>
