Personally I like this idea.

Sounds good, now I just need to remind myself to disable it once r136 comes out.

🤔 Maybe a hint:

I'm not as familiar with the THREE.ImageBitmapLoader, but @lojjic resolved a similar safari 15 black texture issue for us with our custom ImageBitmapLoader by calling ImageBitmap.close() after we used it in our texSubImage2D call when uploading a partial tile to an existing texture or alongside the normal texture.dispose().

    texture.dispose();
    texture.images?.forEach((image: HTMLImageElement | ImageBitmap) => {
      (image as ImageBitmap).close?.();
    });

After those changes we've been able to re-enable ImageBitmap on ios15 and have not heard any problem reports yet in a fairly large number of views?

I'm afraid we can't do that by default (see #22652 (comment)) but it's a good workaround for many use cases.

I would not create more API for this...

I think for the time being I would just check for /Firefox|Safari/.test( navigator.userAgent ) === false here:

Seems like calling .close() is the right solution, but in order to do that we first need #22846.

Sorry for rejecting 😕