Skip to content
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

Second attempt to fix #777, still ensuring the rendering row count is sensible #848

Merged
merged 1 commit into from
Dec 3, 2013

Conversation

dpangier
Copy link

The original issue was that when filtering dropped the filtered row count to under the virtualisation limit the formula used gave the total data source length as a result, leading to potentially very large numbers of rendered rows.

The first attempt to fix misinterpreted the role of various variables, and was incorrect. This led to parts of the grid not rendering under some circumstances.

This fix corrects that misunderstanding, and reverts the original formula but substituting filteredRows.length for data.length still avoiding the rendering of the data source length number of rows.

…w count is sensible - just using a correct interpretation
@dpangier
Copy link
Author

Our testing team has passed this as a fix for issue #777 - please can this be pulled into the main repo?

roblarsen added a commit that referenced this pull request Dec 3, 2013
Second attempt to fix #777, still ensuring the rendering row count is sensible
@roblarsen roblarsen merged commit 769f15d into angular-ui:master Dec 3, 2013
@shuttj shuttj mentioned this pull request Feb 4, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants