Martin Schuhfuss

It seems like there are still people experiencing this Issue and we would like to properly solve this without requiring any of these workarounds. To do this, we need to...

I don't think the maps JS API has this behaviour, so the request would best be directed at the [google maps issue tracker](https://issuetracker.google.com/dashboard/76561?hl=de). It could probably be implemented based on...

TIL! Thanks for pointing this out! Would you be able to create a PR for this?

Thinking about this a bit more, what do we do about more complex cases or dependent intialization, for example ```ts const geocodingLib = useMapsLibrary('geocoding'); const geocoder = useMemo(() => geocodingLib...

Unfortunately, that doesn't work if your content is just a `Pin` component. I should be able to look into this tomorrow.

We're in a bit of a transition-period right now – the version currently in beta will introduce the web-components (`` and ``), and with that we'll probably also get support...

No, it's on my ToDo-list, but I haven't gotten to it yet. I'm still pondering if we should use wrapped events for the markers [like we do for the map](https://github.com/visgl/react-google-maps/blob/f38d3c4004663fd1850c00dca7ddfb7e92b8d5cf/src/components/map/use-map-events.ts#L51-L73)...

Yeah, I'm thinking the same. For the map it was necessary because the map-events mostly don't contain any useful data about the event, but here we have perfectly functional DOM-events...

Thanks for the PR! Can you explain why the listeners should be added to the `Pin` instead of the `AdvancedMarker` component? The way I see it, the `Pin` is just...

Ok yeah, that makes sense. I think there was something with the `pointer-events` css-property that has to be adjusted to use dom-events with the markers. I'll have a look into...