-
-
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
Multiple legends: trace.legend and layout.legend<N> #5098
Comments
It's a good feature and we'd love to have it in the library but it's not on anyone's roadmap at the moment as far as I know. That said, we as maintainers would be happy to help someone from the community to implement it in Plotly.js, or to accept sponsorship to get it on to our short-term roadmap :) |
This issue has been tagged with A community PR for this feature would certainly be welcome, but our experience is deeper features like this are difficult to complete without the Plotly maintainers leading the effort. Sponsorship range: $10k-$15k What Sponsorship includes:
Please include the link to this issue when contacting us to discuss. |
Any plan to work on this issue? |
We'd love to, given a sponsor :) |
Is this going on right now? |
We're still looking for a sponsor, and will update this issue when we find one :) |
Breaking off of #1668 ...
Multiple users have requested what amounts to the ability to have multiple legends, within the current concept of "each trace has a single legend item which appears in a single legend". This could be implemented by adding a
legend
attribute to each trace that would operate similarly to thexaxis
attribute, and a correspondinglegend2
,legend3
series of attributes in thelayout
. This is distinct from the idea of having a legend for size and one for symbol etc, as in that case each item would refer to multiple traces, and each trace would be represented by multiple items.The major challenge here is the default positioning of
legend2
if present... we could do something really ugly like just having it default to the position of the first legend and forcing users to position them manually, but having it "stick to the bottom" is probably a much more graceful solution, if more complex to implement.The text was updated successfully, but these errors were encountered: