Hacker News Reader

Parent Full thread

mlsarecmg

I ran it both in Chrome and Firefox, seems to be working. Could i bother you for error logs?

View on HN

Well, it appears broken for me... But I don't have any errors in the logs.

Firefox 65.0.1 (64bit), Linux (5.0.0).

There are a couple warnings about a particular extension:

> warning: extension `GL_ARB_gpu_shader5' unsupported in fragment shader

The rest just appears to be successful parsing messages.

(But it worked really well in Konqueror & Chromium, so that's something.)

I googled that, looks like an issue in FF: 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.

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.

Reply on news.ycombinator.com