This repository was archived by the owner on Sep 5, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
This repository was archived by the owner on Sep 5, 2024. It is now read-only.
Angular Material causing Google Maps version 3.32 Gesture Handling to not work #11205
Copy link
Copy link
Closed
Labels
resolution: works as expectedThe functionality works as designed and documented.The functionality works as designed and documented.type: gesturesui: mobile
Description
Bug:
- A user is not able to pan on a google maps widget that is used in a web application.
When a web page loads with google maps, if a user tries to pan with a touch and drag gesture, nothing happens. Sometimes, upon dragging, the map will superzoom onto a random spot even. - I am posting a bug here because I noticed that the bug is resolved if Angular Material is removed from the web application. So this told me that there might be some kind of a discrepancy between Angular Material and Google Maps version 3.32 in terms of gesture handling.
What is the expected behavior?
- A user is able to pan, with a touch and drag gesture, on a google maps widget.
What is the current behavior?
- When a user tries to pan on a google maps widget, the map does not move or pan. Sometimes, if a user tries to pan, google maps would superzoom into a random spot and then not allow a user to zoom out.
CodePen and steps to reproduce the issue:
- Google Maps not allowing users on mobile devices to Pan: Link
- Google Maps working great on applications without Angular Material: Link
- Google Maps working great on applications with Angular Material and Google Maps 3.31: Link
Detailed Reproduction Steps:
- Open https://embed.plnkr.co/26e7kL/ on a mobile Android Device
- Try panning on the map
- From my experience, google maps, would not allow users to pan.
Which versions of AngularJS, Material, OS, and browsers are affected?
- AngularJS 1.6.9
- Angular Material 1.1.8
- Google Maps 3.32
- Browsers: Any browser on Android Mobile Devices
What is the use-case or motivation for changing an existing behavior?
Is there anything else we should know? Stack Traces, Screenshots, etc.
- I made a small video explaining the issue:
https://youtu.be/TYfuuY5GHnU - I noticed that this issue is resolved if we use Google Maps version 3.31 instead of 3.32.
- My colleague, Anthony, also noticed that this issue is resolved if we remove Angular Material from the equation while still using Google Maps 3.32.
I am not sure, if this issue is directly related to Angular Material, but I know that it is part of the equation. I already posted a bug report on Google Maps Javascript API, but I also thoguht it might be useful to do it here as well. If you think, this issue is not related to Angular Material, feel free to close it.
rmsmq, freedom-studio and szabi101
Metadata
Metadata
Assignees
Labels
resolution: works as expectedThe functionality works as designed and documented.The functionality works as designed and documented.type: gesturesui: mobile