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

ClusterManagers do not propagate click events (when having overlaying clusters) #394

Closed
cwsiteplan opened this issue Sep 5, 2023 · 4 comments
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@cwsiteplan
Copy link

I do want to cluster markers using specific properties. This results in having multiple ClusterManagers.

These clusterManagers can end up overlaying each other. Like below

The problem is that clusterManagers do not propagate clicks. So only the top-most cluster and their marker can be clicked. (even though markers do not overlay actual markers below)

@cwsiteplan cwsiteplan added triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Sep 5, 2023
@wangela
Copy link
Member

wangela commented Sep 5, 2023

If you would like to upvote the priority of this issue, please comment below or react on the original post above with 👍 so we can see what is popular when we triage.

@cwsiteplan Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

This is an automated message, feel free to ignore.

@kikoso
Copy link
Collaborator

kikoso commented Sep 12, 2023

This is probably related to #294

@kikoso kikoso added priority: p2 Moderately-important priority. Fix may not be included in next release. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. and removed triage me I really want to be triaged. labels Sep 12, 2023
@kikoso kikoso removed the priority: p2 Moderately-important priority. Fix may not be included in next release. label Sep 12, 2023
@cwsiteplan
Copy link
Author

great, that sounds promising!

@kikoso
Copy link
Collaborator

kikoso commented Sep 12, 2023

@cwsiteplan , I am closing this in favor of the older #294. Feel free to follow up on the bugfix there, aiming to merge it soon. Thanks for the patience!

@kikoso kikoso closed this as completed Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

3 participants