[Public WebGL] OffscreenCanvas and shared resources

[Ashley Gullen <ashley@scirra.com>]

I for one am looking forwards to having the ability to do async texture uploads in WebGL, since it's a cause of jank and currently difficult to work around.

It looks like WebGL will be able to run from a worker via OffscreenCanvas (see: https://wiki.whatwg.org/wiki/OffscreenCanvas).

This means with shared resources, we can have a WebGL context running in a worker, post it an image to create a texture from, and then receive back a texture that can be used in a latency-sensitive context (e.g. the "main" context from the main thread or another worker, where it is necessary to render at a steady 60 FPS).

What's the status of shared resources in WebGL and does it need updating to integrate with the upcoming OffscreenCanvas?

Ashley