Partial Page Pagination Causes Incorrect Overall Page Scrolling

[leewyatt]

Description:

Within certain sections of our page, when paging occurs, it results in an undesired scrolling effect on the entire page. This issue becomes particularly pronounced when there's a significant height difference between the current page data and the previous page data, leading to a substantial deviation from our intended "focus" point in the viewport.

Impact:

This scrolling behavior might disorient users,Partial Page Pagination Causes Incorrect Overall Page Scrolling decreasing the overall user experience.

[FlorianKirmaier]

Not sure how to fix it. To me, it seems to behave correctly - so maybe we could just change the UX?

Can you confirm that the behavior is "Correct" but still disorienting?
It's also independent of the web, right?

Having the numbers at the bottom has this effect, when the content size changes, the numbers change their position.
I guess what we would want is, the clicked element - the number, keeps its position. But that sounds very tricky to me.

[leewyatt]

Not sure how to fix it. To me, it seems to behave correctly - so maybe we could just change the UX?

Can you confirm that the behavior is "Correct" but still disorienting? It's also independent of the web, right?

Having the numbers at the bottom has this effect, when the content size changes, the numbers change their position. I guess what we would want is, the clicked element - the number, keeps its position. But that sounds very tricky to me.

Potential Solution:

To mitigate this issue, we can:

1. Anchor a specific node's distance from the top of the viewport.
2. After pagination, recalibrate the distance of this anchored node from the top, ensuring it remains consistent pre and post pagination.

If you have any thoughts, suggestions, or alternative ideas, I'd greatly appreciate your guidance. Let's collaboratively iron out this UX kink!

[dlemmermann]

This should be resolved very generically and you should create a standalone test case where you work only with the ScrollPane and some content that changes its overall height after a user interaction.

[FlorianKirmaier]

IMO this should be provided as an API in the routing.
Something like ScrollingUtils.setPositionAnchor(node). Still working on the method name.

But when this is called, for a short time, like the successive 2 frames, any movement in the scroll position relative to the node gets corrected automatically. Maybe the ScrollPane version of this is also a good candidate for GemsFX or only in the routing.

[leewyatt]

Because node may be recreated. Maybe it would be more reasonable to record the position of the node from the top. scrollto(bounds)/scrollto(x,y)