You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current method for creating a table (e.g. with 'dataSource' and 'matRowDef') doesn't seem compatible with virtual scrolling (e.g. using 'cdkVirtualFor').
Will it be possible to integrate virtual scrolling in an angular table for the table rows?
What is the expected behavior?
Virtual scroll should be compatible with the Angular Material method of creating tables
What is the current behavior?
Difficult to see how to incorporate virtual scroll in an Angular Material table as it doesn't use a *ngFor method
What are the steps to reproduce?= What is the use-case or motivation for changing an existing behavior?
Allow Angular Material tables to benefit from virtual scrolling
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular CLI: 6.2.2
Node: 8.12.0
OS: win32 x64
@angular/material 7.0.0-beta.1
Is there anything else we should know?
The text was updated successfully, but these errors were encountered:
The current method for creating a table (e.g. with 'dataSource' and 'matRowDef') doesn't seem compatible with virtual scrolling (e.g. using 'cdkVirtualFor').
Will it be possible to integrate virtual scrolling in an angular table for the table rows?
What is the expected behavior?
Virtual scroll should be compatible with the Angular Material method of creating tables
What is the current behavior?
Difficult to see how to incorporate virtual scroll in an Angular Material table as it doesn't use a *ngFor method
What are the steps to reproduce?=
What is the use-case or motivation for changing an existing behavior?
Allow Angular Material tables to benefit from virtual scrolling
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular CLI: 6.2.2
Node: 8.12.0
OS: win32 x64
@angular/material 7.0.0-beta.1
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: