This is similar to #229, but will manifest itself when you have multiple tables and persistState enabled.
The issue is that the last table you interact with will update the onPagination stored in local storage. On subsequent refreshes all tables on the page (regardless of their ID) will have the onPagination event triggered with the value from local storage - including having the wrong limit set.
This is similar to #229, but will manifest itself when you have multiple tables and
persistStateenabled.The issue is that the last table you interact with will update the
onPaginationstored in local storage. On subsequent refreshes all tables on the page (regardless of their ID) will have the onPagination event triggered with the value from local storage - including having the wrong limit set.This is also mentioned in a comment on #229.