Martin Schuhfuss

Should be those three. But this might be only temporary, since the [documentation on the legacy features](https://developers.google.com/maps/legacy) says those APIs can no longer be activated for new projects. - [Places...

I've created a new example showing how to use render results from the Routes-API using a simple Polyline component: https://visgl.github.io/react-google-maps/examples/routes-api

Thanks a lot! We'll merge this once the UI Kit components are enabled for our GCP-project.

@FabianKoestring it took a while, but we now have a new version published on npm. If you still experience problems, please report with some more details so we can try...

Yeah, [that's a thing now](https://developers.google.com/maps/legacy). You can make the warning-message go away by removing the `places.Autocomplete` object or replacing it with an implementation based on the new Places API. We...

@paul-vd sure, see here: https://github.com/visgl/react-google-maps/blob/main/examples/autocomplete/src/components/autocomplete-webcomponent.tsx – but note that the component is currently only available in the alpha and beta versions of the Maps API. Also, I think the typings...

@Techsetter as long as you aren't worried about that warning message in the console, there is absolutely no need. I would say, if that part of your functionality is already...

Well - to be fair - Safari 13 is over 4 years old already and, according to the [caniuse usage-table](https://caniuse.com/usage-table), has a 0.07% market share. Officially, the [browser support for...

I guess the important point here is this: If it's the Maps API itself that's no longer working in that browser, there's nothing we can do about it. But if...

No, unfortunately not. At runtime, we can't really know which parts older browsers might have a problem with and it wouldn't really be economical to implement feature-tests for every js-...