Vaadin 24 resets scroll position after rebinding components

[sebastian-gehr]

Description of the bug

After a save operation, the UI logic clears all components from a scroll container and adds them again with a fresh binding. This causes the scroll position of the container to be not retained correctly.

Expected behavior

The scroll position should be retained after save operation and refreshing the content.

Minimal reproducible example

• Open a view containing a vertically scrollable component container.
• Scroll down within that container.
• Trigger a save action.
• During save handling, remove all components from the container.
• Re-add the components with new bindings.
• Observe the scroll position after the update.

Versions

• Vaadin / Flow version: 24.10.0
• Vaadin-CDI version: 15.2.1
• Java version: 17.0.16 aarch64
• OS version: macOS 26.3.1
• Browser version (if applicable): Firefox 149.0
• Application Server (if applicable): Tomcat 10.1.50

[mshabarov]

Could you please elaborate more on what is "save operation" and "fresh bindings" in this context? Also would be simpler for us to investigate if you attach a reproducible example project.

[sebastian-gehr]

ScrollingPositionView.java

You can reproduce the problem in the provided ScrollingPositionView. Clicking the save button rebuilds the content. In Chrome, the scroll position remains the same, but in Firefox, the scrollbar jumps back to the top position.

[sebastian-gehr]

The provide Example ScrollingPosiitionView.java was from a Starter-Project based on Vaadin 25.1.1 and Spring Boot 4.0.5.