What rendering engine are you using?

nubela · on Sept 25, 2014

AOSP webview

higherpurpose · on Sept 25, 2014

Did you fix this? (should be fixed in 4.4+ webview, I think, if that's what you're using for all supported devices)

https://community.rapid7.com/community/metasploit/blog/2014/...

aeling · on Sept 25, 2014

Just tested (using ejj.io/SOP.php), Javelin on my Note 3 isn't vulnerable.

andybak · on Sept 25, 2014

So this will automatically be Chrom(ium) on newer versions of Android?

nubela · on Sept 25, 2014

Yeap, it is already Chromium WebView since 4.4 :) But the performance lags behind bleeding edge Chrome since Google gives its own Chrome a more advanced version of Chromium WebView.

cturhan · on Sept 25, 2014

How did you handle file chooser? As far as I know, WebView disabled fileChooser by 4.4 [1]. This is a problem which we came across today.

[1] http://stackoverflow.com/a/21436901/856702

zethraeus · on Sept 25, 2014

Lags behind Chrome in general in that AndroidWebview doesn't gets single process Chromium, right?

zethraeus · on Sept 25, 2014

*multiprocess

charleslmunger · on Sept 25, 2014

You can build and link in chromium's webview if you want.

nikils · on Sept 26, 2014

Why not create a different rendering engine and replace HTML,CSS, JS ?