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
{{ message }}
This repository was archived by the owner on May 29, 2019. It is now read-only.
First of all, I'm sorry, but I cannot reproduce this issue in plunker.
It also doesn't happen always.
Take a look at the image:
You cannot see it from screenshot, but the next & last buttons have disabled class. If I click on one of them, they still work properly.
Directives total-items attribute is the same scope variable which is shown below as 117
There is about 50% chance that this will happen on page refresh.
Buttons remain disabled even navigation around pages. Only exception is when going to last page in any way and then going back some. Then they appear correctly.
First of all, I'm sorry, but I cannot reproduce this issue in plunker.

It also doesn't happen always.
Take a look at the image:
You cannot see it from screenshot, but the
next&lastbuttons have disabled class. If I click on one of them, they still work properly.Directives
total-itemsattribute is the same scope variable which is shown below as117There is about 50% chance that this will happen on page refresh.
Logic is as simple as in this plunker :http://plnkr.co/edit/vzp4AWwLmRtKnefMbqKp?p=preview
I have empty object at the beginning and after fetching data from db values are assigned.
Buttons remain disabled even navigation around pages. Only exception is when going to last page in any way and then going back some. Then they appear correctly.
Any help will be appreciated.
Version:
1.1.2Angular:
1.4.9