For a long time (I believe well over a year) we’ve been seeing the error below in our monitoring of client-side exceptions. In fact, we’ve seen many thousands of this exception each month. Yet we never get any support calls, so we’ve always believed it has something to do with tear down of the grid or some other aspect which users don’t notice. However, since we see many thousands of these exceptions on a monthly basis, I thought I’d finally reach out and ask you to put in a bit of defensive code before attempting to access the highlight
field in the response to hot.getSelectedRangeLast()
?
We know exactly where the error occurs:
Thanks.