-
Notifications
You must be signed in to change notification settings - Fork 73
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
Overlapping Level 0 ("parent") labels when all children are hidden #177
Comments
Thank you for reporting the problem. |
Hi @KacperMadej if you can give me some clues where to look or which HighCharts axis/tick prototype override should be fixed, I am willing to help with PR |
You might look into Axis' setTickPositions and maybe use the fired event to change something in Highcharts or the plugin. |
Hi @KacperMadej , I have some prototype, tuning it with all my use cases and also with zoom capability of Highcharts. |
I also see no usage. It might be something old and no longer needed or supported. |
Expected behaviour
When all "children" labels are hidden by HighCharts because they would cause overlaps also their "parent" should be hidden
Actual behavior
Parent labels are still visible and overlapping
Live demo with steps to reproduce
Demo: https://codepen.io/bertold8/pen/vYxLoZw
Observe the parent labels - "fish" and "vegetable2" should be imho hidden, because all their children labels are hidden and not be still visible and causing the overlaps
Note
I dont care about the grid, we hide it. Just textual labels are important for me
Product version
"highcharts": "8.2.2",
Grouped Categories v1.1.6 (2020-06-19) - bu even the latest version does not solve the issue
Question
What is this
group.destroyed
meta info used for?https://github.com/blacklabel/grouped_categories/blob/master/grouped-categories.js#L597
I see no usage of it in grouped-categories code. I tried some patch to use it for hiding parent once
parent.destroyed === parent.childCount
but not successful 100%.Thx for any workaround in advance
The text was updated successfully, but these errors were encountered: