Kevin Schneider

This is either achievable by creating one trace per pair, or one trace per group. I settled in implementing one trace per group, as that enables way more useful legends....

Hey @omaus.. Are you still planning to finish this? If not, I would greatly appreciate if you could link what you ended up with during the hackathon (e.g. a script...

Alright, no hurry, just wanted to check in 🚀

The `Title` attribute in plotly.js always refers to the title on top of the whole plot. The reason you see the first title is the logic we use to combine...

> I noted that my variable "allCharts" has a single layout while each chart in "stepCharts" has its own layout with the right title. > > How can I solve...

Good catch, i think the main issue here is that we can only automatically include one version in our docs release process, but the versions of the individual packages have...

Hey @Nick135, thanks for reporting this. I can confirm this as a regression that seems to occur somewhere between 3.0 and 4.0. It seems to be specific for adding multiple...

The root of this bug must be the assignment of new scene ids to the existing charts. The internal logic of `Chart.Grid` combines all charts and adds new unique axis,...

I found the core issue in the output at least. The row number for the scenes is incorrect, while it is correct in the ternary example: with `Chart.Scatter3D`: ```json "scene":{...

found the underlying issue, there are some fixes necessary that are deep in the low-level APIs, see #415 for details. This will be potentially backwards-incompatible and therefore be in v5.