bug(material/autocomplete): Scrolling autocomplete entries does not work when virtual-keyboard is visible
- Vorherrschende Sprache
- TypeScript
- Sterne
- 25k
- Forks
- 6.8k
- Ø Merge
- 1 T. 8 Std.
- Gemergte PRs (30 T.)
- 91
Beschreibung
### 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
Beitragsleitfaden
Rechercherichtung
Beginne mit dem StackBlitz-autocomplete-optgroup-Beispiel und reproduziere das Problem in Android Chrome mit einer virtuellen Tastatur, wobei du das autocomplete nahe am unteren Bildschirmrand platzierst. Vergleiche das Scrollen, wenn die Tastatur sichtbar ist, und identifiziere den beteiligten component- oder overlay-Einstiegspunkt. Erledigt bedeutet, dass die sichtbaren autocomplete-Einträge an dieser Position normal scrollen.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- angular, typescript
- Bereich
- frontend
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 35/100