setDataAtRowProp causes table 'jumps'

Tags: #<Tag:0x00007efc64fd4c30>
#1

Hi,

In my table, in a row, some fields are logically linked. So when edit one cell, other cells get updated as well. There are quite a lot columns ( > 100) in my table, and when I edit one column, there can be dozens of other columns updated.

I use the afterChange hook and call setDataAtRowProp in it to achieve this. But sometimes the table ‘jumps’ when I edit one cell and auto update other cells. It’s like the table automatically quickly navigate back and forth.

Here is link to reproduce it https://jsfiddle.net/crawlregister/nwxLy6uz/4/

You can reproduce it by randomly edit some cells. Each time horizontally scroll towards to end of the row for dozens of columns, pick a random cell and edit. Repeat a few times you will see that after you finish edit, hit the enter, the table ‘jumps’.

I need to the validation on the cell to be triggered and cell be re-rendered. So I update it by call setDataAtRowProp. Not sure if there is any other option.

#2

Thanks for sharing @crawlregister
I reproduced the jumping behavior. That’s an interesting case.

#3

Some additional info.

It happens after upgrade to new pro version. It was working fine with the 0.20.0 version. Here is the jsfiddle https://jsfiddle.net/crawlregister/nwxLy6uz/5/

#4

not actually a PRO version - the change was made in 0.23.0

#5

Yes, agree. That’s why in the jsfiddle to reproduce the problem, I use the 0.24.1 version. It’s not something introduced by PRO.

#6

@aleksandra_budnik what’s the plan for this issue? Any issue raised?

I tried to debug into it, but haven’t find anything useful. Do you have any idea what caused this and any available workaround?

Really don’t want to downgrade the HOT PRO version because such an issue.

Many thanks.

#7

You don’t need to worry @crawlregister
Yesterday I informed about your issue two of our talented programmers. One of them should leave a comment within few hours.

#8

@crawlregister, I was also able to reproduce this issue, and at the first glance it looks like a bug, so I’ve created an issue on GH for it.

You can check the progress on this here: https://github.com/handsontable/handsontable/issues/3405

Thanks for reporting this!

#9