we've been working with angulargrid for a while now and have noticed a very strange, and breaking behavior.
When we load a screen, everything is fine (aside from the fact that we have to explicitly specify a height on images, but that's just a thing we live with)
The screen in question has pagination, when we call our API to load the next page of items, angulargrid kind of freaks out. What that means is the whole grid disappears, a massive area with scrollbars. Here's a short screengrab: http://recordit.co/lqYXBjAjdE
I've noticed this behavior if some API call got called twice, that can confuse angulargrid because it the model is getting updated. But here, the API is only called once, no errors, and the model from call to call is not changing it's the same basic format.
closing this issue in that discovered that the img tags lacked the required class and data-actual-height|width parameters, which was causing much confusion
we've been working with angulargrid for a while now and have noticed a very strange, and breaking behavior.
When we load a screen, everything is fine (aside from the fact that we have to explicitly specify a height on images, but that's just a thing we live with)
The screen in question has pagination, when we call our API to load the next page of items, angulargrid kind of freaks out. What that means is the whole grid disappears, a massive area with scrollbars. Here's a short screengrab: http://recordit.co/lqYXBjAjdE
I've noticed this behavior if some API call got called twice, that can confuse angulargrid because it the model is getting updated. But here, the API is only called once, no errors, and the model from call to call is not changing it's the same basic format.
The markup is pretty vanilla as well:
the directive
news-card
is just a block of HTML:And the controller where the call happens:
Yeah am a bit stumped as to what could cause this very strange behavior. Am I missing anything with respect to the model being refreshed?