-
Notifications
You must be signed in to change notification settings - Fork 44
Description
Bug Report
On Android the native google map positioning disturbs the scrolling experience, which supposedly is a known bug or 'side effect' of the current Android implementation.
→ Video of the problem
→ Discussion about the problem
The real issue
Since I don't think the implementation will be changed in the near future, the most natural fix would be to use the JS implementation for Android users – but that raises the following issues:
1. The Google Maps library is not fully (and correctly) implemented
- Using the plugin I would need specify that the JS version to be used on Android as a config parameter. I can't see that this is possible reading the plugin documentation.
- I should be able to pass the
disableDefaultUI: trueparameter to declutter the map UI and mimic the native experience. - Many types are not implemented according to the Google Maps types, causing unexpected errors and behaviours
2. There's no straight-forward way to target only Android devices
Another alternative is simply to load a different component using the native JS library on Android platforms. But as far as I know, there's no straight forward (or native) way to differentiate between the different platforms.
Recommended solutions
What's the recommended solutions on this topic? Even though this isn't a bug per say, I would argue it's an issue.
Thanks in advance