bug(material-autocomplete): keyboard interaction doesn't work properly when using cdk-virtual-scroll-viewport

angular / components

Component infrastructure and Material Design components for Angular

https://material.angular.io

MIT License

24.37k stars 6.75k forks source link

bug(material-autocomplete): keyboard interaction doesn't work properly when using cdk-virtual-scroll-viewport #16598

Open vekunz opened 5 years ago

vekunz commented 5 years ago

Reproduction

Use StackBlitz to reproduce your issue: https://stackblitz.com/edit/angular-5rmvpq

Steps to reproduce:

Click in the input field to open the autocomplete
On the keyboard click many times on the "down" key or the "up" key

Expected Behavior

If the focus goes beyond the visible viewport, the list should automaticly scroll down/up

Actual Behavior

It just doesn't scroll, and if the end of the actuall renderd items is reached, it comes back to the start and doesn't render new items.

By the way we had to implement a little hack that the virtual viewport is correctly rendert at all. It is the (opened)-Event at the mat-autocomplete you can see in the stackblitz example.

Environment

Angular: 8.x
CDK/Material: 8.x
Browser(s): Tested in Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Tested with Windows

leonardochaia commented 5 years ago

Any updates on this matter? will it be addressed on any upcoming release?

Thank you!

jhernandez73 commented 4 years ago

Hi! Any update on this issue ?

vekunz commented 4 years ago

Any updates on this?

Splaktar commented 4 years ago

This is currently unsupported and blocked by https://github.com/angular/components/issues/10122. It's unknown at this time if, once virtual scrolling is supported by mat-autocomplete, users will be able to provide their own cdk-virtual-scroll-viewport.

babudurairaji commented 5 months ago

Hi All,

We have been using Angular 17 and Angular Material 14.2.7 in our application. The same issue exists in the latest version as well. Is it possible to provide a workaround solution or prioritize this issue as high and provide a fix?

brobeans1320 commented 3 months ago

Hi All,

We have been using Angular 17 and Angular Material 14.2.7 in our application. The same issue exists in the latest version as well. Is it possible to provide a workaround solution or prioritize this issue as high and provide a fix?

I found this in another thread as a workaround, doesn't seem like it'll be fixed anytime soon unfortunately. https://www.npmjs.com/package/ngx-virtual-select-field