1343905 - Figure out the deal with WebVR and WebRender integration

Status: RESOLVED WORKSFORME

(Core :: Graphics: WebRender, enhancement, P3)

Description

[Kartikaya Gupta (email:[e-mail])]

Quoting from Kip's dev-platform post:

"Windows only support for WebVR would be enabled by default in Firefox 54.  OSX is not yet supported by current VR headsets.  Beta Linux support for HTC Vive has very recently landed, and will be supported by Firefox after the Firefox 54 uplift."

Do we know how this will interact with webRender? I know the VR code touches a lot of the compositor codepaths and if we're enabling it in 54 we presumably can't regress it with WebRender. I don't know if VR handling has come up much or at all in previous WebRender discussions - I can't remember anything offhand.

Comment 1

[Milan Sreckovic [:milan] (needinfo for best results)]

WebVR team will keep up with our changes; we'll just make sure we don't break automated tests or introduce build errors.

Comment 2

[:kip (Kearwood Gilbert)]

At least with the features we've enabled currently in WebVR, there won't be much (if any) interaction between WebRender and WebVR.

WebGLContext, TextureChild, TextureParent, TextureHost, and HTMLCanvasElement are the major hook-points for WebVR.

Future expansion of WebVR will fit on the output-end of WebRender, to support capture of individual elements and entire web pages as textures to be reprojected and composited with VR and Mixed-Reality content.

Comment 3

[:kip (Kearwood Gilbert)]

I'm currently implementing a smoke test that works without having physical VR hardware connected:

https://bugzilla.mozilla.org/show_bug.cgi?id=1343356

This should catch most issues that might regress; however, it is unlikely to be caused by WebRender work.

Comment 4

[Kartikaya Gupta (email:[e-mail])]

Ok, I guess we might as well close this out then, since there's nothing that really needs to be done in this bug.