Older versions of three.js (versions r109 to r111) attempt to feature-detect and use the OffscreenCanvas API. However this breaks in Nightly since it seems the API implementation is partial or incompatible. The error occurs while three.js is initializing, which means it breaks three.js-based apps entirely. This will cause issues with our Mozilla Hubs Cloud product as well, since some users choose to use older custom client code. The error message is `Uncaught TypeError: OffscreenCanvas.getContext: '2d' (value of argument 1) is not a valid value for enumeration OffscreenRenderingContextId.` The error can be reproduced in Nightly with this example page: https://rawcdn.githack.com/mrdoob/three.js/r111/examples/webgl_materials_envmaps_hdr.html Cannot be reproduced in Firefox Stable or Chrome.
Bug 1747431 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Older versions of three.js (versions r109 to r111) attempt to feature-detect and use the OffscreenCanvas API. However this breaks in Nightly since it seems the API implementation is partial or incompatible. The error occurs while three.js is initializing, which means it breaks three.js-based apps entirely. This will cause issues with our Mozilla Hubs Cloud product as well, since some users choose to use older custom client code, which uses older versions of three.js. The error message is `Uncaught TypeError: OffscreenCanvas.getContext: '2d' (value of argument 1) is not a valid value for enumeration OffscreenRenderingContextId.` The error can be reproduced in Nightly with this example page: https://rawcdn.githack.com/mrdoob/three.js/r111/examples/webgl_materials_envmaps_hdr.html Cannot be reproduced in Firefox Stable or Chrome.
Older versions of three.js (versions r109 to r111) attempt to feature-detect and use the OffscreenCanvas API. However this breaks in Nightly since it seems the API implementation is partial or incompatible. The error occurs while three.js is initializing, which means it breaks three.js-based apps entirely. This will cause issues with our Mozilla Hubs Cloud product as well, since some users choose to use older custom client code, which use older versions of three.js. The error message is `Uncaught TypeError: OffscreenCanvas.getContext: '2d' (value of argument 1) is not a valid value for enumeration OffscreenRenderingContextId.` The error can be reproduced in Nightly with this example page: https://rawcdn.githack.com/mrdoob/three.js/r111/examples/webgl_materials_envmaps_hdr.html Cannot be reproduced in Firefox Stable or Chrome.
Edit: This bug was initially filed to report issues with the three.js library, but as commented below, we've found that it breaks several other libraries and sites. Older versions of three.js (versions r109 to r111) attempt to feature-detect and use the OffscreenCanvas API. However this breaks in Nightly since it seems the API implementation is partial or incompatible. The error occurs while three.js is initializing, which means it breaks three.js-based apps entirely. This will cause issues with our Mozilla Hubs Cloud product as well, since some users choose to use older custom client code, which use older versions of three.js. The error message is `Uncaught TypeError: OffscreenCanvas.getContext: '2d' (value of argument 1) is not a valid value for enumeration OffscreenRenderingContextId.` The error can be reproduced in Nightly with this example page: https://rawcdn.githack.com/mrdoob/three.js/r111/examples/webgl_materials_envmaps_hdr.html Cannot be reproduced in Firefox Stable or Chrome.