You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updating the zorder property on existing traces only works for go.Scatter traces but not for go.Scattergl traces. The same command may therefore fail or succeed, simply depending on the number of traces.
The difference between the two is that the first creates simple go.Scatter traces, whereas the second dataframe is so large that plotly tries to use go.Scattergl traces. Those however do not accept the zorder property (see also the documentation of go.Scattergl).
If for some reason the zorder cannot be implemented on go.Scattergl graph objects, then plotly should just not provide it and instead warn the user. The same code resulting in behaviour depending on the size of the dataframe passed is really unexpected and can be tedious to debug.
zorder option is only available for SVG traces. WebGL based traces e.g. scattergl do not have this option.
It may possible to consider adding it.
But that would be a feature request.
Updating the
zorder
property on existing traces only works forgo.Scatter
traces but not forgo.Scattergl
traces. The same command may therefore fail or succeed, simply depending on the number of traces.This works as expected:
This returns error
Bad property path: zorder
:The difference between the two is that the first creates simple
go.Scatter
traces, whereas the second dataframe is so large that plotly tries to usego.Scattergl
traces. Those however do not accept thezorder
property (see also the documentation ofgo.Scattergl
).If for some reason the
zorder
cannot be implemented ongo.Scattergl
graph objects, then plotly should just not provide it and instead warn the user. The same code resulting in behaviour depending on the size of the dataframe passed is really unexpected and can be tedious to debug.This issue may also be linked to #1514.
The text was updated successfully, but these errors were encountered: