> the parent document of the worker that receives the OffscreenCanvas implicitly sets the rAF rate to it's own rAF makes Offscreen Canvas unsuitable for WebVR (which seems pretty bad) Not really. WebVR forces you to use it own requestFrame API, which controls the frame rate. This would also be the case with OffscreenCanvas. > To what extent does WebVR want/need OffscreenCanvas support? It would be a killer combo, and at one point this was a part of the plan, but the current version of the WebVR spec has no dependencies OffscreenCanvas and does not expose anything in Workers. No idea what happened there. I know there are vendors implementing WebVR who have not yet committed to implementing OffscreenCanvas, but I don't see why that would prevent the WebVR+OffscreenCanvas option from being planned. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/141#issuecomment-338045442
Received on Thursday, 19 October 2017 21:38:24 UTC