-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add way to configure trace module ordering within subplot #3748
Comments
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 |
That'd be awesome 👍 Perhaps worth adding to #420? |
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 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 |
I could likely manage with that |
Addressed by #6918 |
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#866The text was updated successfully, but these errors were encountered: