Bug description
Description: After fetching the latest demo（only frontend demo,never update the newest backend demo!） from the master branch, the user interface for the pagination buttons appears correctly. However, the functionality for server-side pagination on tables is broken.
Steps to Reproduce:
- Create a table.
- Enable the "Server Pagination" option.
- View the table on a dashboard.
- Click any of the server pagination buttons (e.g., next page, previous page).
Screenshots/recordings
https://github.com/user-attachments/assets/f7c90ca0-63f5-4320-b86c-556b27de82c8
No response
Superset version
master / latest-dev
Python version
3.9
Node version
18 or greater
Browser
Chrome
Additional context
No response
Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: dosubot[bot]
This is a known bug in the latest Superset master: when server pagination is enabled for table charts, clicking the pagination buttons does not update the table, even though the backend returns the correct data and the pagination controls update properly. The issue is a frontend state synchronization problem—pagination button clicks update state, but the table doesn't re-render with new data, likely due to a bug in how serverPaginationData or setDataMask is handled in the frontend. This regression has been reported in several recent issues and discussions (#31626, #32513, #34102).
Workarounds like toggling server pagination off and on, refreshing the chart, or increasing the "server page length" setting sometimes help, but are not reliable. The bug is under active discussion and investigation, but there is no official fix yet. If you see any errors in the browser console when clicking the pagination buttons, sharing those details in the relevant issue could help maintainers track down the root cause.
You can follow progress or add details to the main tracking issues:
#31626
#32513
#34102
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
