Given the recent thread on "customer pain points", I'd suggest that this capability be released when there is confidence that it works well, and any breakages are understood and minimized. Reading the other threads, sounds like it's not quite there yet.
On May 1, 2014, at 10:02 AM, Michal Mocny <mmo...@chromium.org> wrote: > Should we just be cautious and bump to 3.6, or do we give you till Monday? > > > On Thu, May 1, 2014 at 9:54 AM, Ian Clelland <iclell...@chromium.org> wrote: > >> Currently, I think that pluggable webview is a non-starter for 3.5.0; >> there's an unfortunate backwards-incompatibility introduced by abstracting >> CordovaWebView from a class into an interface. >> >> /me swears at Java for not having either multiple inheritance or non-static >> fields on interfaces... >> >> I'm playing with one possible solution to this today; if it works, then we >> might be able to get this in to 3.5, but I'm not 100% confident yet. I'll >> have to let you know later today.
