Hi Maria,
The fact that:
strongly suggests you're dealing with a regression introduced in the Data Widgets module rather than an issue in your page design.
One thing I'd investigate is whether the newer widget version is causing the component to be fully re-rendered when the page number changes. When React-based widgets are recreated instead of simply refreshing their data source, the browser often loses the previous scroll position and resets the container to the top.
A few diagnostic tests I'd try:
Since you've confirmed reverting to 2.27.4 immediately fixes the issue, my practical recommendation would be to stay on 2.27.4 for that application until the cause is identified or a newer release resolves it.
If you haven't already, I'd also suggest raising a GitHub issue (if the Data Widgets repository is being used) or a Mendix support ticket with:
That's exactly the kind of version-specific behavioral change that widget maintainers can usually verify quite quickly.
From what you've described, this looks much more like a scroll-position regression introduced in Data Widgets v2.27.5 than a configuration issue in your application.