bug(MatSelect): When panel is displayed inside a SideNav, it stays opened on Escape button
- Lenguaje dominante
- TypeScript
- Estrellas
- 25k
- Forks
- 6.8k
- Merge medio
- 1 d 8 h
- PR fusionados (30 d)
- 91
Descripción
### 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
Hi,
When using MatSelect inside a SideNav, if the panel is opened and we close the sideNav with the Escape button, the MatSelect panel stays opened.
I expected the same behavior like with the MatDatePicker, if the picker panel is opened, when using Escape the picker is closed first, and then using Escape again closes the sideNav.
I also provide the same sample inside a Dialog using the MatSelect and MatDatePicker and in this case, both works the same way and correctly.
The issue seems related to this one:
https://github.com/angular/components/issues/7981
Thanks
### Reproduction
StackBlitz link: https://stackblitz.com/edit/components-issue-starter-r9az1u4q
Steps to reproduce:
1. Click on button to open the SideNav
2. Open the MatSelect panel
3. Click on Escape
### Expected Behavior
MatSelect should be closed with the escape button instead of the SideNav
### Actual Behavior
SideNav is closed and MatSelect panel stays visible
### Environment
- Angular: 18 (same issue in 19)
- CDK/Material: 18 (same issue in 19)
- Browser(s): Chrome
- Operating System (e.g. Windows, macOS, Ubuntu): Windows
Guía de contribución
Línea de trabajo
Comienza con la reproducción vinculada de StackBlitz y reproduce la secuencia de Escape en los ejemplos de SideNav, MatSelect y MatDatePicker. Compara cómo MatSelect gestiona Escape con el comportamiento del picker. Se considera terminado cuando el panel de MatSelect se cierra primero y un Escape posterior cierra la SideNav, incluida la cobertura de la configuración indicada.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- angular, typescript
- Área
- frontend
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Bien especificado
- Aptitud para principiantes
- 45/100