:jrmuizel's sense is that worker usage is going to be pretty common for WebGPU content. His feeling is that, while it would be fine to ship to release with WebGPU available only on the main thread, we shouldn't announce WebGPU support until it is available in workers. Since we have removed all wgpu interaction from the content process, it seems to me that worker support should be quite straightforward. I would want to audit our canvas interactions, but otherwise our DOM API implementation just doesn't interact with anything but IPDL.
Bug 1818042 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
:jrmuizel's sense is that worker usage is going to be pretty common for WebGPU content. His feeling is that, while it would be fine to ship to release with WebGPU available only on the main thread, we shouldn't announce WebGPU support until it is available in workers. That seems reasonable to me. Since we have removed all wgpu interaction from the content process, it seems to me that worker support should be quite straightforward. I would want to audit our canvas interactions, but otherwise our DOM API implementation just doesn't interact with anything but IPDL.