Polymer certainly used to work with cca (we fixed bugs to make sure it did), and we've been using it recently so this must be a regression / environment issue. I haven't tried it on vanilla cordova.
Regarding WebView and chromium versions, there's a very exciting project in the pipeline (read on!), but here are the full details:
(0): WebView on Android 4.3 or lower is not based on chrome at all.
(1): KitKat WebView up to 4.4.2 is based on Chrome 30, but some features are turned off (like WebGL, WebRTC).
(2): KitKat WebView 4.4.3 seems based on Chrome 33. As far as I know this is still an internal dogfood that has not shipped yet.
(3): Android L-Release is intended to ship with an auto-updating Chrome WebView, which I assume with update alongside the browser update schedule.
(4): We (cordova team) are playing with bundling a build of chromium alongside your application, leveraging a project called
crosswalk. This means you get build your app with your own webview based on Chrome 35+, with WebGL, WebRTC, etc, and will run on devices all the way back to ICS (4.0) of Android! It does means an extra ~18Mb to your binary and fewer opportunities to share memory with other apps, but for devs it means you don't have to deal with legacy webview or different webview implementations on various client machines. Until L-release auto-update WebView, this will likely be a huge hit with hybrid app developers.
> cd mobile-chrome-apps
> git checkout crosswalk
> git submodule update --init
> npm install
> npm link
> cd ..
Now you should have a global install of `cca` that will automatically use crosswalk. Now create a project and try it out as usual:
# You must have Android SDK set up already -- if you've ever created a cca/cordova android project before, you should be alright.
> cca create HelloWorld
> cd HelloWorld
> cca run android
I encourage everyone to try this, since we (cordova team) intend to promote development of polymer based hybrid apps using crosswalk a lot this year.
Good Luck, Have fun!