bug(material/autocomplete): Scrolling autocomplete entries does not work when virtual-keyboard is visible
- Langage dominant
- TypeScript
- Étoiles
- 25k
- Forks
- 6.8k
- Merge moyen
- 1 j 8 h
- PR mergées (30 j)
- 91
Description
### 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
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par l’exemple d’optgroup d’autocomplete de StackBlitz et reproduisez le problème sur Android Chrome avec un clavier virtuel, en plaçant l’autocomplete près du bas de l’écran. Comparez le défilement lorsque le clavier est visible et identifiez le point d’entrée du component ou de l’overlay concerné. C’est terminé lorsque les entrées visibles de l’autocomplete défilent normalement à cette position.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- angular, typescript
- Domaine
- frontend
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 35/100