bug(material/autocomplete): Scrolling autocomplete entries does not work when virtual-keyboard is visible
- 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
When using the mat-autocomplete on a mobile device and the auto-complete is not at the top of the screen. Then the scrolling of the autocomplete does not work or the point where the autocomplete can be scrolled is below the autocomplete.
https://github.com/angular/components/assets/51996054/3acabe93-5328-487a-999c-a2cfe4ea0355
### Reproduction
StackBlitz link: https://material.angular.io/components/autocomplete/examples#autocomplete-optgroup
I was not able to reproduce it at StackBlitz maybe it has something todo with the stucture and the scrolling areas of the page.
Steps to reproduce:
1. Open it on an device with an virtual keyboard
2. click in the autocomplete of "Option groups autocomplete" when its in the bottom part of the screen
### Expected Behavior
Expected to scroll the autocompletion entries whenever the autocompletion entries are visible.
### Actual Behavior
Actual the scrolling does not work as expected.
https://github.com/angular/components/assets/51996054/3acabe93-5328-487a-999c-a2cfe4ea0355
### Environment
- Angular: 17.0.4
- CDK/Material: 17.0.4
- Browser(s): Chrome (120.0.6099.115)
- Operating System (e.g. Windows, macOS, Ubuntu): Android
Guía de contribución
Línea de trabajo
Comienza con el ejemplo de optgroup de autocomplete de StackBlitz y reproduce el problema en Android Chrome con un teclado virtual, colocando el autocomplete cerca de la parte inferior de la pantalla. Compara el desplazamiento cuando el teclado está visible e identifica el punto de entrada del component o overlay involucrado. Se considera terminado cuando las entradas visibles del autocomplete se desplazan normalmente en esta posición.
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
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 35/100