Markers: Conflicting console warnings for AdvancedMarkerElement click event registration

[JoeEarly]

Environment details
API: Maps JavaScript API / Markers
OS: macOS Darwin 25.2.0
Library version: Maps JS API v=weekly (loaded Feb 2025), @googlemaps/markerclusterer@2.6.2

Steps to reproduce

1. Create a map with mapId and AdvancedMarkerElement
2. Register a click handler using marker.addListener('click', ...) (as recommended by Google's own a11y warning)
3. Observe console warning: : Please use addEventListener('gmp-click', ...) instead of addEventListener('click', ...)
4. Switch to marker.addEventListener('gmp-click', ...) to fix the above warning
5. Observe new console warning: To make AdvancedMarkerElement clickable and provide better accessible experiences, use addListener() to register a "click" event
6. Additionally, addEventListener('gmp-click') does not make markers clickable - clicks do not fire

Code example

const { AdvancedMarkerElement } = await google.maps.importLibrary("marker")

const marker = new AdvancedMarkerElement({
  position: { lat: 54.0, lng: -4.5 },
  map,
  title: 'Test marker',
  content: myElement
})

// Option A: warns "Please use addEventListener('gmp-click', ...)"
marker.addListener('click', () => { console.log('clicked') })

// Option B: warns "use addListener() to register a click event" + clicks don't fire
marker.addEventListener('gmp-click', () => { console.log('clicked') })

Stack trace

// Warning from Option A:
<gmp-advanced-marker>: Please use addEventListener('gmp-click', ...) instead of addEventListener('click', ...).
_.xn @ main.js:194
addListener @ marker.js:99

// Warning from Option B:
To make AdvancedMarkerElement clickable and provide better accessible experiences,
use addListener() to register a "click" event on the AdvancedMarkerElement instance.

Summary: There is no way to register a click handler on AdvancedMarkerElement without triggering a console warning. addListener('click') is the only option that actually works (fires events, sets up a11y) but it produces a deprecation-style warning suggesting gmp-click. Using addEventListener('gmp-click') silences that warning but produces the opposite warning and markers become non-clickable.

[amitpurex]

I am getting same console warning as soon as I add the (mapClick) on map-advance-marker
<map-advanced-marker #marker="mapAdvancedMarker" [position]="center()" [options]="advancedMarkerOptions" (mapClick)="openInfoWindow(marker)" />

[gityopie]

Hi @JoeEarly,
Did you manage to resolve the issue?
As described in the console warning message, "..use addListener() to register the click event.."
In your code sample (Option B) you used addEventListener.

Try:
marker.addListener('gmp-click', () => { console.log('clicked') }

[bdcoder2]

According to the docs, when creating the marker, it must be made "clickable" by setting the gmpClickable option property to true (it is false by default). For example:

const marker = new AdvancedMarkerElement({
  position: { lat: 54.0, lng: -4.5 },
  map,
  title: 'Test marker',
  content: myElement,
  gmpClickable: true   // <--- Required to make marker "clickable" and trigger "gmp-click" events
})

// Click events will now fire WITHOUT console warnings  ...
marker.addListener( 'gmp-click', () => { console.log('clicked') })

The above should mitigate the console warnings.