Hi Mary,

Yes, this is currently how the Conditional works, if you visually set the rows which fall under this criteria to hide.
They are only visually hidden, but the table will still 'count them' for the table pagination.
So, in this case, as you described, we can see on the first few pages of the table, there are always 10 rows showing, and when we reach some hidden ones - they are just visually hidden and for example the page 8 only shows 3 rows, while the other 7 are hidden because of the Conditional Rule.

So, technically speaking, the row count is not disrupted - The table still 'respects' each Page as it is coming from the table's original row count.

So, for example, there are still 10 rows on the 8th page of the Table, so each 'unique row ID' is on its respective Table Page.

This way, let's say if Page 8 has row ID's ( if each row is auto increment ID) rows from 71 to 80;
So row ID's from 74 to 80 are hidden on this Page;

Then next Page 9 was starting with unique row ID 81, 82 and up until 90 for the 'tenth row' on table Page 9;
they will still remain on the same Table's Page as they were before your conditional Rule is applied.


If you wish to see a better solution/improvement in how this works, you can leave a development suggestion and we will do our best to work on it in the future.
We just can't say an ETA on it.

Please feel free to search on our suggestions page, 

 to see if someone may be already suggested this feature. If you can't see it, feel free to add your suggestion there,  and as more people vote, the feature will move higher on the priority list.

You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.