-
Notifications
You must be signed in to change notification settings - Fork 20
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
Does not work with collisionBehavior on vector maps #493
Comments
Mobiletainment
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
Apr 9, 2022
@Mobiletainment Thank you for opening this issue. 🙏
This is an automated message, feel free to ignore. |
I tried to inspect how the collision behavior works, but neither of these approaches was successful:
It would be really nice if google maps exposed an event for changes in the collisions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you for the library.
I'm currently using the vector maps with the new Marker Collision Management which is currently in beta.
My use case is that I have many markers and I'm using the collision behavior
google.maps.CollisionBehavior.OPTIONAL_AND_HIDES_LOWER_PRIORITY
to hide overlapped markers with lower priority.This works well for markers constructed as
google.maps.Marker
without any labels. As soon as I start to use labels withMarkerWithLabel
, I'm seeing leftover labels for markers which are hidden.The following example shows the collision behavior where only 2 markers remain visible while 11 markers should be hidden:
google.maps.Marker
:MarkerWithLabel
:Environment details
@googlemaps/markerwithlabel": "2.0.9
Steps to reproduce
Please check out the beta documentation for Marker Collision Management which is used as a base for this example.
Code example
Thank you for your support.
The text was updated successfully, but these errors were encountered: