-
Notifications
You must be signed in to change notification settings - Fork 865
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
When switching data sources dir-pagination-controls displays wrong number of results #208
Comments
This is happening because I think $watch should be updating the now empty collection and it is not:
|
As a workaround I hide the pagination control when there are 0/null results with
|
After more research I see that |
Hi, Thanks for the detailed report. Is it possible to make a Plunker demo of this? I cannot tell from what you wrote, but are there multiple dir-paginations being used in the same view? If so, are the |
I will work on a plunker reproduction of the issue. This page only has 1 dir-pagination, however there are at least 2 others used in the site. I see three active, uniquely named paginationid's in the |
The code below displays 37 pages when
vm.totalResults
is zero. The issue only happens in one scenario:ng-if
go to another user with 0 resultsWhy is this happening?
The text was updated successfully, but these errors were encountered: