I actually don&#x27;t care too much about getting WebGL out of the main UI thread. I&#x27;m doing WebVR work, so I always need the UI thread to be completely responsive, to always be ready to update the camera with regards to the motion sensor.<p>However, this being able to push the text rendering I do off to a thread, specifically to keep the main thread responsive, would be huge for me: <a href="https:&#x2F;&#x2F;bugzilla.mozilla.org&#x2F;show_bug.cgi?id=801176" rel="nofollow">https:&#x2F;&#x2F;bugzilla.mozilla.org&#x2F;show_bug.cgi?id=801176</a><p>I&#x27;m already working on physics in a web worker, and have already got picking working there. The text rendering would be the biggest piece of low-hanging fruit in my rendering latency.<p>EDIT: whoa, I just had a vision of having the text rendering canvas running in a new tab, using HTMLCanvasElement.toBlob() to serialize it, and transmitting from one tab to another through SharedWorker or even LocalStorage. It&#x27;s a huge hack, and it will depend on whether or not the comms and deserialization is not more expensive than the rendering, but could potentially solve my problem <i>today</i>.