Using restyle method in updatemenus button removes the modebar

[HunterMcGushion]

This is very similar to #3824, and this bug was first reported in this comment by @sermeor, but I thought it made sense to open a new issue.

The issue can be reproduced on the Plotly website in the "Restyle Button Single Attribute" example.

On initial load, hovering over the plot brings up the modebar.

However, after clicking the "Heatmap" button, the modebar no longer appears.

The same thing happens when changing the trace type in other examples on this page.
This issue can also be reproduced in this Plotly Python example. Please let me know if I should open a separate issue on plotly.py.

Thank you for your time and for making Plotly so awesome!

[archmoj]

@HunterMcGushion thanks for the report.

[ArtOshchepkov]

Is there any workaround?

[Yook74]

The modebar is removed when switching from any type of 3D plot to any kind of 2D plot, but not vice-versa.

I have not tested every possible combination of 3D and 2D plot types, but I have (programmatically) checked all combinations of
bar, scatter, heatmap, scatter3d, surface, and mesh3d. The modebar is removed only when switching from a 3D type to a 2D type.

When I say that the modebar is "removed," I mean that its contents are no longer present in the DOM. The modebar-container div is there, but it has no contents. I've looked into the relevant code a little and it looks like when switching between 2D and 3D, makePlotFramework is called. This clears the modebar-container div. When going from 2D to 3D, the div is then filled in again, but for some reason it is not populated when switching from 3D to 2D.

The modebar will remain missing as long as one calls react, restyle etc. The modebar will show up again when newPlot is called or until the config parameter displayModeBar is set to false and then true again.

@ArtOshchepkov the last paragraph details the only workaround I know of. Just call newPlot instead of restyle. This does not work for me though, since I'm using Dash and do not have direct control over the Plotly API calls, so a fix would be appreciated!