When client side pagination is enabled, the tooltip_conditional filter will cause "TypeError: Can not read property of undefined" exception when try to navigate to next page. It is fine on the first page though.
Run the program and try to navigate to the second page, you will see the error prompt by developer tool.
I did a bit debugging with Chrome developer tool. The exception is at this line.
More specifically, on the first time when this line is executed after navigating to the second page, it has row = 3, virtualized.offset.rows=0 and virtualized.data array containing only one row (i.e. the only row in the second page), which makes virtualized.data[row - virtualized.offset.rows] to access beyond the array tail and hence the exception.
I suspect the line should be changed to something like virtualized.data[row - virtualized.indicies[0] - virtualized.offset.rows], but I'm not familiar with the code base enough to tell whether this is a proper fix.
When client side pagination is enabled, the tooltip_conditional filter will cause "TypeError: Can not read property of undefined" exception when try to navigate to next page. It is fine on the first page though.
A sample example to reproduce the problem.
Test environment:
Run the program and try to navigate to the second page, you will see the error prompt by developer tool.
I did a bit debugging with Chrome developer tool. The exception is at this line.
More specifically, on the first time when this line is executed after navigating to the second page, it has
row
= 3,virtualized.offset.rows
=0 andvirtualized.data
array containing only one row (i.e. the only row in the second page), which makesvirtualized.data[row - virtualized.offset.rows]
to access beyond the array tail and hence the exception.I suspect the line should be changed to something like
virtualized.data[row - virtualized.indicies[0] - virtualized.offset.rows]
, but I'm not familiar with the code base enough to tell whether this is a proper fix.