Mojtaba Samimi

@LiamConnors Please take over this PR and once ready merge it into your doc PR or master? I thought you may want to revert big commit of plotly.js update [ba9c413](https://github.com/plotly/plotly.py/pull/4726/commits/ba9c413ced84eb5e0a2abef1df5a310971fbf47e)...

This is also related to `geo` subplots not `map` & `mapbox`. @ndrezn Please keep track of this ticket.

Is this the duplicate of https://github.com/plotly/plotly.js/issues/4760?

I'm not sure we should consider this a bug. Here is a [codepen](https://codepen.io/MojtabaSamimi/pen/JjQRXVW?editors=0010) illustrating the graph using plotly.js. You could use an array to specify desirable `textposition` as illustrated in...

Thanks @stephprobst for the report and details.

@alexcjohnson In respect to you comments I improved the handling of NaNs in parcoords `constraintrange` in [890ccfd](https://github.com/plotly/plotly.js/pull/7131/commits/890ccfda3ece78beccb86bd368b582aac8de6ebf). In the case of stackgl these NaN conditions appear to occur for the...

Good news: I found this bug as labeled P1 on `chromium.org`. See https://issues.chromium.org/issues/361823993

@alexcjohnson @gvwilson With the revert updates in https://issues.chromium.org/issues/361823993 we may be able to close this PR. But I am still not sure how they are going to update the latest...

This is now fixed by Chromium `128.0.6613.113`: https://chromium.googlesource.com/chromium/src/+/refs/tags/128.0.6613.113 I was able to update my Chrome. Closing.

@birkskyum, There are now conflicts on this branch after merging your recent PRs. BTW if I recall karma is adjusted with esbuild.