On the new UIs, tables re render and reset when UI updates or table data changes. This resets the scroll and makes the screen jump.
Working with long lists is very hard, this is very noticeable in IX suggestions table where accepting a suggestion down the scroll will make it jump all the way up again.
@konzz @aphilop I'm listing here some of the new IX issues that might be workable withing the context of this issue.
6809 I think right now we are manually constructing the footer with the paginator and element counter. We can still do that, but have the table return things like the number of rows so they are not built from outside. Or maybe delegate this entirely to the table (with the option of handling pagination state externally for URL pagination).
6812 This could be because we are handling rows with positions instead of a given ID? I've been looking at how the table library does dnd and it relies on every element of the table having a unique ID.
6806 Might be an easy fix
6807 This will likely be related to how we are making the table take vertical space right now and could be fix in this issue.
On the new UIs, tables re render and reset when UI updates or table data changes. This resets the scroll and makes the screen jump.
Working with long lists is very hard, this is very noticeable in IX suggestions table where accepting a suggestion down the scroll will make it jump all the way up again.