4 ms·
I googled that, looks like an issue in FF: https://github.com/mrdoob/three.js/issues/9716 https://github.com/mrdoob/three.js/issues/9716 Basically i just channe
by mlsarecmg 8y ago
I googled that, looks like an issue in FF: https://github.com/mrdoob/three.js/issues/9716 https://github.com/mrdoob/three.js/issues/9716 Basically i just channel through regular three without creating much of a dependency. If it doesn't work in react-three-fiber, then i doesn't work in threee-js. But they're so big that usually these webGL bugs are either fixed quickly by them, if it's their fault, or they're filling vendor issues.
- shakna 8y agothree.js have marked it as a wontfix and referred it onto Firefox. It's sitting in Bugzilla as a 6-month+ old bug. Safari and Chrome both had to work around the same thing, so it seems like there's some contention around who is to blame here. Either way, three.js is (partially) broken for Firefox users.