What can cause DataTable info to be off?
What can cause DataTable info to be off?

I've noticed something odd when I'm filtering data. I have attached an img of the issue. The final tally is correct but when scrolled to the bottom I see that there may be an issue. "121 to 87" shouldn't happen. I was wondering what could I have done that may cause it to happen?
I am using http://cdn.datatables.net/1.10.9/css/dataTables.bootstrap.min.css for this page. I cannot provide a link to this page due to it residing on my company's intranet.
This discussion has been closed.
Answers
Sounds like you might be doing server side processing. If so, then probably the place to start is with the 3rd FAQ here:
https://datatables.net/faqs/#Server-side-processing
Please post your findings or further questions.
Kevin
I am not using SSP. I'm doing ajax. The filter is being applied after the data is rendered. I do not use SSP due to its performance issues I encountered when searching using our data model.
What "performance issues"? I haven't encountered any.
It just didn't work for our needs.
We would need a link to a page showing the issue so it can be debugged. The only thing I can think of that would cause that problem would be using Scroller with irregularly sized rows, or perhaps an out of date row height calculation. But really we'd need a link to the page to understand what is going wrong.
Allan
Unfortunately, the page is an internal company website.
I'm not sure there is much help I can offer without a way to reproduce the error. Can you reproduce it on http://live.datatables.net, JSFiddle, CodePen or similar?
Allan
I don't think I'll be able to. I have other filtering options working with my DT and they work correctly meaning that the "Showing..." piece works normal. Its very odd I'll say.
I fear that there isn't any help I can offer in that case. I'd need a way to either reproduce the error or view the error to be able to offer any support.
Allan
Understandably so. Thanks anyways. I was trying to see if anyone can point me in the right direction.
Can you run the debugger on the page? That might give me some idea of what is happening - maybe...!
Allan