I’m getting a “WebGL is not supported by your browser” error message, even though your test page displays fine and I also see the scatter plot momentarily before the error message replaces it. It’s very frustrating as I’m recommending adoption of your library to my employer.
I’m using Chrome Version 80.0.3987.132 (Official Build) (64-bit).
I am seeing “WARN: webgl setup failed possibly due to enabling preserveDrawingBuffer config. The device may not be supported by is-mobile module! Inverting preserveDrawingBuffer option in second attempt to create webgl scene.” in the console, don’t know if that helps? And I occasionally notice the correct render for an instant before the warning message replaces it.
Here is a screenshot of the WebGL scatter plot that appears before being replaced by the error message. Very frustrating and this thread seems to be being ignored?
I was not able to replicate this problem.
Would you please try some oldest plotly.js minor versions on this codepen to see if any of them works on your machine?
All the other plotly examples (except 3d scatter) work in my “Create React App” based application.
Even 3d scatter works for an instant sometimes (as you can see from the screenshot), I’m using basically the same code as in the plotly example, only in a “Create React App” application.
I suspect something in the Plotly library is looking at the usage environment and then deciding it’s not suitable (even though it plainly is!).
And here is the 3d scatter plot working perfectly in codepen!
Sorry @archmoj, not sure how best I can do that as it’s webpack/node. Is there a plotly version number corresponding to that that I can set in package.json?
In your package.json,
you may try replacing
“plotly.js”: “^1.57.0”,
with
“plotly.js”: “git://github.com/plotly/plotly.js.git#8fcc3d86b2299ddc57c82647ef849ce36e3f5fb6”,
Save it.
Then npm install or yarn install depending on which one you use.
Thanks we are getting somewhere.
Now let’s try
“plotly.js”: “git://github.com/plotly/plotly.js.git#07a32308592f05d378eb990d3677fb1d9586d8d4",
to show the underlying webgl error.