Repository navigation
Add way to configure trace module ordering within subplot #3748
Description
For example, although the scatter trace appears first, it is drawn on top of the box-plot https://codepen.io/cpsievert/pen/yrVpeb
Needed for ggplotly() parity plotly/plotly.R#866
Activity
etpinard commentedon Apr 8, 2019
Yep, that's how things work unfortunately for now.
Here's our ordering:
plotly.js/src/plots/cartesian/constants.js
Lines 65 to 74 in e111300
I guess we could add a list-like attribute to configure the module ordering, or better yet honor the ordering found in
gd.data(but that would be a breaking change).cpsievert commentedon Apr 8, 2019
That'd be awesome 👍
Perhaps worth adding to #420?
alexcjohnson commentedon Apr 9, 2019
Not sure this is a good idea. For one there are cross-trace interactions that sometimes make this impossible (or at least nonsensical) - mostly involving filled
scatter*but stacked bar would also do weird things in certain cases.I also worry people would accidentally lose point-like traces behind area-like traces, and that in some contexts like chart studio it could be hard to get the order you want.
So I'd prefer we keep the current behavior but add a way to stack it as desired. Can we just add something like a
zindexattribute - where any matching values keep the current behavior but different values (within a subplot) stack by index?cpsievert commentedon Apr 9, 2019
I could likely manage with that
[-]Some traces (e.g. box, violin, bar) always appear below other traces[/-][+]Add way to configure trace module ordering within subplot[/+]emilykl commentedon May 24, 2024
Addressed by #6918