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

fix: advanced marker position can be null #903

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

LeLunZ
Copy link

@LeLunZ LeLunZ commented Jul 29, 2024

Fixes #902 🦕

Currently there is still a problem with the tests.
As google.maps.Markers and google.maps.marker.AdvancedMarkerElement are inconsistent in their way of handling the position.
.getPosition on google.maps.Marker returns a LatLng(lat=0, lng=0) even if no position was provided.
While google.maps.marker.AdvancedMarkerElement .position really is null.

If a fix like the one provided in the PR would be accepted, the tests needs to be changed because of the inconsistency.

Copy link

google-cla bot commented Jul 29, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

AdvancedMarker position null messes up cluster location
1 participant