Assigned
Status Update
Comments
l....@triply.at <l....@triply.at> #2
When I wrote “(even if the marker is placed somewhere else on the map),” I was referring specifically to adjusting the marker’s anchor point (nothing else). In other words, although the marker’s visible position shifts on the map, its wrapper element (...-marker-view) remains in the original position and continues to block click events in the newly exposed areas.
In our testing if "pointer-events: none" would be applied to the wrapper element with class ...-marker-view, that would fix the issue and the visible elements below would be clickable.
la...@google.com <la...@google.com>
la...@google.com <la...@google.com> #3
Thank you for posting.
We are currently looking into this and will get back to you as soon as we have an update.
Description
When creating an AdvancedMarkerElement without a click listener, the marker’s wrapper element (with the class ...-marker-view) blocks click events for any underlying elements or the map itself (even if the marker is placed somewhere else on the map).
This issue is problematic because the recommended approach to adjust a marker’s anchor is:
marker.style.transform = 'translateY(50%)';
However, applying this transform does not move the ...-marker-view container. As a result, an invisible area above the marker remains unclickable, preventing clicks from reaching underlying elements or the map.
Google Maps Version: 3.59.8
jsfiddle:https://jsfiddle.net/6yhw2nLc/
In this example, the wrapper of the marker which is below, intercepts clicks for another marker which would be clickable and is not hidden on the screen by anything. In other words, the red button should be clickable, but some wrapper of the blue button is in the way, which prevents clicks.
We’d appreciate any guidance or fixes regarding this behavior.