three.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 th

three.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.