Well, I think we NEED to support third-party WebViews as a first step. If I don't hear any objections, I'm going to merge 4.0.x into master tomorrow, and start a discuss thread for the 4.0.x release. I believe all we really need to do right now is make sure that the CookieManager issues are resolved (without a Factory please, we've gone 5 years without using that Java anti-pattern).
As for the WebView, I don't want to inherit one, but at the same time I don't really want to rely on Intel and XWalk. This is definitely an internal conversation that I'm sure is going on (or should be going on) at all our workplaces right now, and I'd be interested in hearing what people's thoughts are about having the "One true WebView". On Mon Jan 26 2015 at 11:22:45 AM Marcel Kinard <cmarc...@gmail.com> wrote: > I just read Adrian Ludwig's post on Plus, I now feel worse about Jelly > Bean users. On one hand, we could communicate all over about loading only > trusted content into the webview, but I think that will be ignored by a lot > of devs. On the other hand, we could provide our own webview by default for > 4.0 and above. That would require we drop support for Gingerbread (which > I'm not necessarily against), but also brings with it ownership of the > webview and us delivering security patches for it. Or maybe by default > prevent non-local content from being loaded into the webview. Sigh. > > > On Jan 24, 2015, at 3:33 PM, Joe Bowser <bows...@gmail.com> wrote: > > > > More about WebKit and Jellybean not being updated. This is the same line > > we've been saying, but a lot of users have been completely disregarding. > > So, I don't know where we should go from here: > > > > https://plus.google.com/117193854832907724231/posts/1md7ruEwBLF > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
