Skip to content

virtualizationThreshold not working? and a bug when bigger then data list #5588

New issue

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

Open
Ruud-cb opened this issue Jul 28, 2016 · 1 comment
Open

Comments

@Ruud-cb
Copy link

Ruud-cb commented Jul 28, 2016

Noticed when virtualizationThreshold is set to a larger or equal number then the data length, it will cause serious unresponsive lag. The plunker, which is a fork of issue #5585 (scroll lag), will have a hard time loading. The virtualizationThreshold is set to 1001, data list begins with 1000 and increases. When the data list is larger then 1001 it returns back to normal, with scroll lag.

https://embed.plnkr.co/wmxIyxz7GGQc1r8oytUf/

That's one issue, the other issue is that it is not working, I guess? As far as I know the virtualizationThreshold should render the amount of rows it is set to? Yet it seems it does not render more than is visible because it still shows white rows when scrolling (thus rendering new rows). I might be wrong here?

@angular-git-user
Copy link

angular-git-user commented Aug 16, 2016

Yes the virtualization threshold will render number of rows it has been set to... making the grid unresponsive if there are too many rows bcoz it has to create dom for each row... the best approach is to leave the virtualizaiton threshold to default.. and let the grid render each row as you scroll down.. since this was the primary feature of ui-grid..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants