bug(google-maps): Warning in Console about adding Event-Listener for click instead of gmp-click

[phrei]

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

I'm getting the following warning in console when I use @angular/google-maps@19.2.2:

<gmp-advanced-marker>: Please use addEventListener('gmp-click', ...) instead of addEventListener('click', ...).

Would this mean the following code should be changed to gmp-click as suggested in the warning?

components/src/google-maps/map-advanced-marker/map-advanced-marker.ts

Line 136 in 1b721a0

this._eventManager.getLazyEmitter<google.maps.MapMouseEvent>('click');

Reproduction

Create a project that uses the (mapClick)-Output on a <map-advanced-marker>

Expected Behavior

No warning in console.

Actual Behavior

Warning in console.

Environment

• Angular: 19.2.1
• CDK/Material: 19.2.2
• Google-Maps: 19.2.2
• Browser(s): Chrome
• Operating System: Windows

[crisbeto]

Hmm interesting, something along these lines came up for #30420 and we couldn't use addEventListener, because it was only available in the beta channel of the Maps API.

[crisbeto]

Playing with it a bit more, even when using addEventListener('gmp-click') it behaves weirdly. The handler doesn't get fired and it still logs some warning from the clusterer.

[king-martinien]

Hello,
I’m experiencing the same issue with <gmp-advanced-marker> in @angular/google-maps@19.2.2.

My setup:

• Angular version: 19.1.3
• @angular/google-maps version: 19.2.2
• • Browser: Chrome

[martinarcejoviva]

I'm experiencing the same issue on a Nuxt app using google maps. Even though I don't use .addListener("click",
I still get those warnings.