I have a few dcc.Graphs that render histograms in my Dash app. In one instance, I have a callback that will update a shape on the histogram if the proper data exists in dcc.Loading.
Upon updating the callback, the relayout of the graph will look something like this:
however, on a tab change within the app, upon returning to the tab with the histogram, the relayout of the histogram has updated to:
{'autosize': True}
despite having no logic within the callbacks to allow a callback on a tab change. This continues to occur even by limiting callbacks to no include certain actions such as:
ctx.triggered_id != "tabs"
where tabs is the id of the tab set.
This is odd because the shape that is declared in the callback is not removed or modified in any way, but the change to the relayout affects a number of other linked callbacks erroneously.
I have a few dcc.Graphs that render histograms in my Dash app. In one instance, I have a callback that will update a shape on the histogram if the proper data exists in dcc.Loading.
Upon updating the callback, the relayout of the graph will look something like this:
however, on a tab change within the app, upon returning to the tab with the histogram, the relayout of the histogram has updated to:
despite having no logic within the callbacks to allow a callback on a tab change. This continues to occur even by limiting callbacks to no include certain actions such as:
where tabs is the id of the tab set.
This is odd because the shape that is declared in the callback is not removed or modified in any way, but the change to the relayout affects a number of other linked callbacks erroneously.