bug(select): mat-select.close() emits openedChange event with value "true"

[nileshlad09]

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

CDK/material: "19.0.5"

Description

unexpected behavior calling the close() method on mat-select. it emits openedChange event with value "true"

Reproduction

StackBlitz link: https://stackblitz.com/edit/oirpsfkv?file=src%2Fexample%2Fselect-disabled-example.html,src%2Fexample%2Fselect-disabled-example.ts,package.json
(forked from Material Docs)

Steps to reproduce:
Open the console.
Click on the mat-select.
Observe the console logs — after a single click, multiple open and close events are fired.

Expected Behavior

After one click, there should only be two logs: one open and one close.

Actual Behavior

Multiple open and close logs appear after a single click.

Environment

Angular: 19.2.20
CDK/Material: 19.2.19
Browser(s): Chrome, Firefox
Operating System (e.g. Windows, macOS, Ubuntu): Windows 11

[crisbeto]

The reason this happens is that we have a click listener on the select trigger and on the mat-form-field that both call the open method. Even though open has some guards to protect from it being called twice in a row, it doesn't work because you're calling close immediately so by the time the click reaches the mat-form-field it is considered closed.

I tried a few different approaches to resolve this in #33119, but they were all too breaking for internal tests so I suspect that we won't be able to land any of them.

That being said, you can work around it for your own code if you add (click)="$event.stopPropagation()" to the mat-select.