Thanks for the report!

I suspect this error is fatal, as in the parcoords trace completely fails to render. @webbres can you confirm?

I don't have access to Chrome 66 at the moment, so I can't confirm. Is anyone else noticing this in Chrome 66?

The call stack seems to point to a regl call - which we also use for scattergl and splom traces. @webbres (or anyone else with Chrome 66) would mind opening

• https://rreusser.github.io/plotly-mock-viewer/#gl2d_12
• https://rreusser.github.io/plotly-mock-viewer/#splom_0

to see if the same error occurs?

@etpinard yes either the entire plot fails to load or the lines are missing but selections can be made on the coordinates.

I will report back on the remaining questions when I get access to PC again.

Cheers

Sam

Link 1:

Uncaught (in promise) TypeError: Cannot read property 'regl' of null
at new Scatter (plotly-latest.js:80026)
at module.exports (plotly-latest.js:79968)
at Object.plot (plotly-latest.js:177605)
at plotOne (plotly-latest.js:131617)
at Object.exports.plot (plotly-latest.js:131585)
at exports.drawData (plotly-latest.js:125440)
at Object.lib.syncOrAsync (plotly-latest.js:116132)
at Object.exports.plot (plotly-latest.js:121078)
at (index):434

Link 2:

plotly-latest.js:80026 Uncaught (in promise) TypeError: Cannot read property 'regl' of null
at new Scatter (plotly-latest.js:80026)
at Scatter (plotly-latest.js:80013)
at new SPLOM (plotly-latest.js:80941)
at SPLOM (plotly-latest.js:80930)
at plotOne (plotly-latest.js:180837)
at Object.plot (plotly-latest.js:180778)
at Object.plot (plotly-latest.js:180221)
at exports.drawData (plotly-latest.js:125440)
at Object.lib.syncOrAsync (plotly-latest.js:116132)
at Object.exports.plot (plotly-latest.js:121078)
Scatter @ plotly-latest.js:80026
Scatter @ plotly-latest.js:80013
SPLOM @ plotly-latest.js:80941
SPLOM @ plotly-latest.js:80930
plotOne @ plotly-latest.js:180837
plot @ plotly-latest.js:180778
plot @ plotly-latest.js:180221
exports.drawData @ plotly-latest.js:125440
lib.syncOrAsync @ plotly-latest.js:116132
exports.plot @ plotly-latest.js:121078
(anonymous) @ (index):434
Promise.then (async)
plotMock @ (index):425
plotFromHash @ (index):441
module.exports @ (index):485
2../viewer @ (index):319
s @ (index):34
e @ (index):34
(anonymous) @ (index):34

cc @dy scattergl, splom and parcoords appear broken in Chrome 66.

We should try to find a solution before ASAP.

Ok that works from my chrome 66 windows 7.
Waiting for other reports.

I've just upgraded from one version of 66 to Version 66.0.3359.139 and the issue is resolved on windows 10.

Thanks for the update @webbres

I'll leave this issue open in case other users hit similar issues with Chrome 66.

I can confirm that upgrading the Chrome version on the windows 7 machines experiencing the same issue has also resolved the issue. Seems to have been specific to 66.0.3359.117.

Thanks for the quick response, glad it didn't end up being a hassle.

This issue may have been a bit more complex than I thought. Adding extra info in case anyone else has a similar issue.

I am now getting this error occurring in the latest Chrome only through a remote desktop session and only on parallel coords (whereas it happened with and without remote desktop and on the test plots asked about).

The demo plots work fine via remote desktop.

I'm not really familiar with WebGL but it looks like this isn't a plotly issue so much as a WebGL issue (though we do still have one machine that refused to work locally even after a uninstall and install of chrome).

turning off hardware acceleration triggers the issue without remote desktop

As a sidethought - it would be really nice to have regl-parcoords component.

Closing as this issue seems to be resolved in Chrome versions released after 66.0.3359.117.

@webbres feel free to open another issue about the problems you're facing in a remote desktop.