Is this gjs-view3d support IE11 ?

[naver]

Is this gjs-view3d support IE11 ?

[RudyBlack]

@ctxwing
To my knowledge, the IE11 browser is not Evergreen brower. So, as "View3D is available for the last two major versions of all evergreen desktop and mobile browsers, " it means not including IE11.

[WoodNeck]

As @RudyBlack explained, View3D doesn't support IE11.
This is mostly due to features that three.js@r134's GLTFLoader uses.
You can try using polyfills for missing features.

Still, even if you successfully support IE11 with polyfills or something, you can't use optimization features for your models that use WASM like KTX2 basisu or Meshopt/Draco,

[ctxwing]

As @RudyBlack explained, View3D doesn't support IE11. This is mostly due to features that three.js@r134's GLTFLoader uses. You can try using polyfills for missing features.

Still, even if you successfully support IE11 with polyfills or something, you can't use optimization features for your models that use WASM like KTX2 basisu or Meshopt/Draco,

Thank you both @RudyBlack , @WoodNeck for the quickest response I've ever seen.^^;
I got understood that
""the egjs-view3d does not support IE11, because IE11 is not Evergreen Browser and becuase of the three.js@r134's Loader issue."

I had not applied WASM features. that is to say, just using glb ( converted by FBX2glTF with option --binary) and no extra features such as Draco compression.

Could I apply missing feature by using polyfill as @WoodNeck recommend ? . I am just novice and do not know how to ...
Supporting IE11 is the one of big issue of my customer's claim.

I gently ask that how to implement polyfill to support IE 11, to make best of egjs-view3d ..

thanks again so much ..

[WoodNeck]

We can support IE11 by using an older version of three.js, I don't know the exact version that three.js dropped IE11 support, but it's pretty sure that the version we're using(r134) is not supporting IE11.
However, as IE11 is officially dead, we're not planning to add support in the future.
Also, we need more features that the newer three.js provides.

So, here're some approaches that you can try:

• Add polyfills
  • Load View3D in the IE11, and add polyfills for the missing es6+ features like Promise, etc.
• Fork View3D and downgrade the three.js version.
• Convince your client to drop IE11 support.