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
When updating scattergl plots in Firefox, some traces do not render as expected. This issue does not appear in other browsers, such as Chrome or Edge, where the scattergl traces are rendered as expected. When using scattergl, certain traces may not be displayed properly, resulting in missing visualizations on the graph despite their presence in the data. This issue is particularly noticeable with scattergl plots utilizing WebGL rendering.
The problem is absent when using scatter traces, which rely on SVG rendering, suggesting a potential WebGL compatibility or rendering issue specific to Firefox. The observed behavior occurs consistently across different datasets and setups, suggesting a deeper compatibility problem between WebGL rendering in Firefox and the Plotly scattergl implementation. Furthermore, there are no error messages in the browser console during the issue.
When updating
scattergl
plots in Firefox, some traces do not render as expected. This issue does not appear in other browsers, such as Chrome or Edge, where thescattergl
traces are rendered as expected. When usingscattergl
, certain traces may not be displayed properly, resulting in missing visualizations on the graph despite their presence in the data. This issue is particularly noticeable withscattergl
plots utilizingWebGL
rendering.The problem is absent when using
scatter
traces, which rely on SVG rendering, suggesting a potentialWebGL
compatibility or rendering issue specific to Firefox. The observed behavior occurs consistently across different datasets and setups, suggesting a deeper compatibility problem between WebGL rendering in Firefox and the Plotlyscattergl
implementation. Furthermore, there are no error messages in the browser console during the issue.Here is a really simple reproducing example:
https://codepen.io/Puneet-Sharma112/pen/NWQOyVv
I also see a related issue which was created long back but was closed as non-reproducible.
The text was updated successfully, but these errors were encountered: