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
{{ message }}
Repository navigation
[BUG] dcc.Graphfigure prop may include Plotly.js _inputArray for typed arrays #5676
When a dcc.Graphfigure data contains typed arrays (for example int8, float32, etc.), the figure can include a Plotly.js internal field _inputArray
In the example below, the _inputArray is included after user interaction but not when the figure is first rendered.
_inputArray duplicates bdata and also includes decoded data, increasing callback payload size and overhead for large datasets.
Possible fixs:
strip _inputArray in dcc.Graph before updating the figure prop. But that might be considered a breaking change since some people are now using _inputArray in callbacks.
Have an option to not encode np arrays when using dash. This will also fix the issue of customdata not being available is clickData, hoverData if they are np arrays
changed the title [-][BUG] `dcc.Graph` callback payload may include Plotly.js `_inputArray` for typed arrays[/-][+][BUG] `dcc.Graph` `figure` prop may include Plotly.js `_inputArray` for typed arrays[/+]on Jun 26, 2026
Activity
[-][BUG] `dcc.Graph` callback payload may include Plotly.js `_inputArray` for typed arrays[/-][+][BUG] `dcc.Graph` `figure` prop may include Plotly.js `_inputArray` for typed arrays[/+]AnnMarieW commentedon Jun 26, 2026
Here's a proposal for a function to decode a typed array in a dash callback:
robertclaus commentedon Jul 23, 2026
Thank you for the write-up @AnnMarieW . We'll likely need to fix this in plotly.py.
AnnMarieW commentedon Jul 23, 2026
@robertclaus
That makes sense. Would you like me to close this here?
camdecoster commentedon Jul 30, 2026
@AnnMarieW we transferred the issue over, so no need to close it.
emilykl commentedon Sep 2, 2026
Related: #5124