bump libs for WebVR API v1.0

[cvan]

r? @dmarcos @ngokevin

[cvan]

when this is merged upstream, we'll point back to boris'

[cvan]

@ngokevin @dmarcos can we merge?

[cvan]

I want to merge this, but it looks like Brandon's still got several bugs to address with webvr-polyfill and THREE.VREffect.

Using the latest Oculus Chromium build, scenes using THREE.VREffect do not render correctly in the Oculus headset. See my comment in Brandon's PR: mrdoob/three.js#8221 (comment) In the headset, the image appears super enlarged. I tried the webvr_cubes three.js WebVR example (http://threejs.org/examples/#webvr_cubes) with Brandon's branch, and I couldn't get the scene to render correctly. I also tried hooking it up to Sechelt and A-Frame scenes - same issue. It might be worth adding a three.js WebVR scene to Brandon's webvr-samples repo. (I filed https://github.com/toji/webvr-samples/issues/13 to add a three.js test scene.)

The changes to THREE.VREffect in the PR currently do not work in Firefox (nor in the deprecated Chromium WebVR builds, but I know that's not an issue). See my comment here: mrdoob/three.js#8221 (comment)

The changes to webvr-polyfill in the PR currently do not work in Firefox (nor in the deprecated Chromium WebVR builds, but I know that's not an issue). See my comment here: immersive-web/webvr-polyfill#33 (comment)

Also, looks like Brandon's making some changes directly to webvr-polyfill in the webvr-samples directory.

[ngokevin]

Should we bother merging this for 0.1.x?

[cvan]

Should we bother merging this for 0.1.x?

well, all A-Frame sites don't/won't work in the Chromium builds. so I think we should.