There are a number of path-dependent issues with changes to mode and errorbars in scattergl traces. All of these investigations start from the gl2d_error_bars mock. Regular scatter traces can show errorbars even if mode='none' ie everything else is hidden:
If I just load that mock and restyle(gd, 'mode', 'none') everything disappears:
But if I first change to type: 'scatter', mode: 'none' and then go back to scattergl the errorbars are still there:
Other mode changes can create all sorts of oddities (including different behavior for orphan points):
cc @etpinard @dy
There are a number of path-dependent issues with changes to
modeand errorbars inscattergltraces. All of these investigations start from thegl2d_error_barsmock. Regularscattertraces can show errorbars even ifmode='none'ie everything else is hidden:If I just load that mock and
restyle(gd, 'mode', 'none')everything disappears:But if I first change to
type: 'scatter', mode: 'none'and then go back toscatterglthe errorbars are still there:Other mode changes can create all sorts of oddities (including different behavior for orphan points):
cc @etpinard @dy