We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug. The cdk-virtual-scroll does not behave correctly when sizing is done by flex-layout in certain case.
The VirtualScroll will have the full height of all the items instead of taking the size of the available.
Only take the place given by the flex-layout
Here is a StackBlitz : https://stackblitz.com/edit/angular-virtual-scroll-and-flex-layout
Note: if the Virtual Scroll is not inside the "listComponent" div, it will resize correctly.
Angular 6.0.7 Material 6.3.2 Flex-Layout 6.0.0-beta.16 OS: Windows Browsers : Firefox 61.0, Edge 42.17134.1.0
The text was updated successfully, but these errors were encountered:
Seem to be a flex-layout issue. workarounds specified in angular/flex-layout#689 seem to fix the issue for now.
Sorry, something went wrong.
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
No branches or pull requests
Bug, feature request, or proposal:
Bug. The cdk-virtual-scroll does not behave correctly when sizing is done by flex-layout in certain case.
The VirtualScroll will have the full height of all the items instead of taking the size of the available.
What is the expected behavior?
Only take the place given by the flex-layout
What is the current behavior?
What are the steps to reproduce?
Here is a StackBlitz : https://stackblitz.com/edit/angular-virtual-scroll-and-flex-layout
Note: if the Virtual Scroll is not inside the "listComponent" div, it will resize correctly.
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 6.0.7
Material 6.3.2
Flex-Layout 6.0.0-beta.16
OS: Windows
Browsers : Firefox 61.0, Edge 42.17134.1.0
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: