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: don't use potentially unreliable addListener functions #158

Merged
merged 2 commits into from
Jan 17, 2024

Conversation

usefulthink
Copy link
Collaborator

As discovered in #137, there are apparently situations where the .addListener() function that components inherit from the MVCObject class will return undefined in certain edge cases, like when the Map is rendering the fallback-screen for an invalid API-key.

Therefore we will use the hopefully more stable google.maps.event.addListener method everywhere.

As discovered in visgl#137, there are apparently situations where the `.addListener()` function that components inherit from the MVCObject class will return undefined in certain edge cases, like when the Map is rendering the fallback-screen for an invalid API-key.

Therefore we will use the hopefully more stable `google.maps.event.addListener` method everywhere.
src/libraries/google-maps-api-loader.ts Outdated Show resolved Hide resolved
Co-authored-by: Malte Modrow <malte.modrow@gmail.com>
@usefulthink usefulthink merged commit 7309efa into visgl:main Jan 17, 2024
2 checks passed
@usefulthink usefulthink deleted the fix/add-listener branch January 17, 2024 10:25
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.

None yet

2 participants