PropertyMixer unsupported Array methods break Internet Explorer 11
See original GitHub issueDescription of the problem
Thank you @c-morten for implementing additive animations! We hope to use it in the future.
Unfortunately it has broken animation for Internet Explorer 11, because Array.prototype.fill
and Array.prototype.copyWithin
were used in the PropertyMixer
. If this is a deliberate decision to drop support for Internet Explorer 11 without polyfills (in src
, for some files in examples
you need polyfills anyway), it would be nice to mention this in the migration guides, so updating doesn’t unknowingly break Internet Explorer 11 in production.
Three.js version
- Dev
- r116
- …
Browser
- All of them
- Chrome
- Firefox
- Internet Explorer
OS
- All of them
- Windows
- macOS
- Linux
- Android
- iOS
Hardware Requirements (graphics card, VR Device, …)
Issue Analytics
- State:
- Created 3 years ago
- Comments:17 (8 by maintainers)
Top Results From Across the Web
Fixing JavaScript Array functions in Internet Explorer (indexOf ...
There are a number of workarounds here and there, but I'd like to fold a proper, canonical set of implementations into our site...
Read more >JavaScript Arrays - W3Schools Tryit Editor
The Array.from() method returns an array from any iterable object. ... The Array.from() method is not supported in Internet Explorer 11 (or earlier)....
Read more >Full text of "Adobe Director 11.5" - Internet Archive
These function names exposed through the Xtras are not supported in Unicode. ... You can view the Explorer panel in the Dictionary view...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Here’s the PR with the fix: https://github.com/mrdoob/three.js/pull/19297
It would be easy enough to replace the calls to fill and copyWithin with a forloop and just use set, which appears to be supported across the board. I can submit a PR with that change.