Skip to content
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

Treemap: border set for data point is overlapping other points #4211

Closed
KacperMadej opened this issue May 20, 2015 · 4 comments
Closed

Treemap: border set for data point is overlapping other points #4211

KacperMadej opened this issue May 20, 2015 · 4 comments
Labels
Status: Stale This issue hasn't had any activity for a while, and will be auto-closed if no further updates occur. Type: Undecided

Comments

@KacperMadej
Copy link
Contributor

Border set for data point is overlapping other points and zIndex of points is changing because of hovering over points.
Example: http://jsfiddle.net/kzoon/p9cgg9pe/3/

@TorsteinHonsi
Copy link
Collaborator

Highcharts tree maps are designed to put the hovered square on top, in order to have the border above other borders. This is clear with another example: http://jsfiddle.net/p9cgg9pe/6/.

@jon-a-nygaard Maybe we should disable individual borderWidth settings on points?

@jon-a-nygaard
Copy link
Contributor

@highslide-software It would simplify and avoid some visual problems if all points had the same borderWidth. But that would also mean that we should disable it for the levels options also.

A more complicated option, which in a way is also more correct, is to include the borderWidth into the calculation of the plotting area of each point.

@TorsteinHonsi
Copy link
Collaborator

But that would also mean that we should disable it for the levels options also.

I don't think so, because as long as all visible points in the view have the same borderWidth, it's okay. The problems starts when there are points with different border widths visible at the same time at the same level.

@stale
Copy link

stale bot commented May 16, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

@stale stale bot added the Status: Stale This issue hasn't had any activity for a while, and will be auto-closed if no further updates occur. label May 16, 2019
@stale stale bot closed this as completed May 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Stale This issue hasn't had any activity for a while, and will be auto-closed if no further updates occur. Type: Undecided
Projects
None yet
Development

No branches or pull requests

3 participants