Martin Schuhfuss

Sounds good. Should also apply for the `onDrag*` events as interaction props.

As far as I know, the issue in #419 has been resolved upstream in the maps API itself. Are you still seeing that warning-message?

And you're saying it is severely affecting your app, can you elaborate on that a bit? I was under the impression that the original issue only happens occasionally when aggressively...

Thanks a lot. That's an error-message I haven't yet seen, and a very helpful one at that. Let me see if I can figure out how it's even possible that...

I have the feeling there are different issues at play here. If I recall correctly, the initial problem appears to have had something to do with the browser handling the...

Very cool, thanks a lot! Did you see that only in iOS Safari (I'm assuming a current version(?)), or are other browsers affected as well?

I already spent some time with it, and it seems somewhat reproducible with lots of stuff going on on the map. However, I haven't yet found a good way to...

The camera-logic of the Map-component works like this: 1. when the user interacts with the map, it will emit `bounds_change` events 2. react-google-maps receives those events and updates an internal...

@ronlv10 thanks a lot for investigating and your summary. A combination of blocking the main thread and time-sensitive computations like acceleration could indeed explain this behavior. If that is the...

The second link you shared (https://codesandbox.io/p/github/qiaoxin136/login-map/main?workspaceId=d68df01c-f46f-497c-bfee-4134267b36a9) is returning an error "Insufficient access". Can you check if the workspace is publicly available? You can verify this yourself by opening it in...