You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Andrew Grieve <ag...@google.com> on 2012/08/23 17:37:08 UTC

Changing default JS->Native bridge mode on iOS

Looks like some users have found that it fixes their problem:

https://issues.apache.org/jira/browse/CB-593

Options are:
1) Leave default as the iframe and tell users to change it if it causes
them problems
2) Change the default to the iframeless version. It's a bit slower, but
still quite fast.
3) Have the default be based on their OS version.


I'd like to go with #2 because I think iframes have been the source of
trouble for more bugs than just this CSS scrolling one (I've seen them mess
up touch events on android before).

Any objections?

Re: Changing default JS->Native bridge mode on iOS

Posted by Shazron <sh...@gmail.com>.
I vote for #2, with a note in the 2.1 upgrading docs just in case on
how to change it back. I'm planning a 2.1 iOS overview blog post as
well, I can have a section for this.

On Thu, Aug 23, 2012 at 8:37 AM, Andrew Grieve <ag...@google.com> wrote:
> Looks like some users have found that it fixes their problem:
>
> https://issues.apache.org/jira/browse/CB-593
>
> Options are:
> 1) Leave default as the iframe and tell users to change it if it causes them
> problems
> 2) Change the default to the iframeless version. It's a bit slower, but
> still quite fast.
> 3) Have the default be based on their OS version.
>
>
> I'd like to go with #2 because I think iframes have been the source of
> trouble for more bugs than just this CSS scrolling one (I've seen them mess
> up touch events on android before).
>
> Any objections?