Bug when using rowreorder extension together with the scroller extension

[dandulo]

Hello,

there is a bug when using rowreorder extension together with the scroller extension.
Example to reproduce bug:
https://jsfiddle.net/99358x8p/10/

To reproduce the bug use the following steps:

1. Drag first row to a position greater than row 30.
2. Scroll up to the top row.
3. You can see identical and wrong sequence numbers everywhere. The ordering/data is broken.

It works if you only reorder the row to a near position. At what distance the bug occurs depends on the scrollY value of the datatable. With smaller scrollY value the bug occurs sooner.

Is there any workaround?

Many thanks for any answer. Best regards.

Unfortunately yes, RowReorder and Scroller don't play nicely together at the moment. Scrollers "virtual rendering" messes with RowReorder's reordering, thus the problem.

I'm afraid there is no workaround.

[dandulo]

Ok. I hope this will be fixed in the future. That would be amazing. RowReorder is such a great feature but slow without scroller in large tables (and useless with pagination, because you cannot drag to another page).

Thanks anyway for the great work and fast answer!
Regards Daniel

[Kranthi32]

Any update on this issue.

[AllanJard]

No. Any updates would be noted here.

The two are basically not compatible when trying to reorder beyond the Scroller draw buffer. I don't see how they could be made to work in such a case, particularly if server-side processing was involved.