dxc-technology
[DxcPaginator] Paginator select becomes unresponsive when number of pages is too large
Describe the bug Paginator component becomes unresponsive when number of pages is too large(100k+)
To Reproduce Steps to reproduce the behaviour.
- Set number of items to 1million (1000000)
- enable showGoToPage
- Click gotoPage select/dropdown.
- It can be observed, the whole browser slows down, and dropdown scroller also doesn't refresh quickly.
- This reduces the responsiveness and impacts the usability of the app.
Expected behaviour Restore the responsiveness of the component or a different UI control/interaction in paginator to choose page numbers when number of pages is very large(say 100k). Also good to add few test cases in cdk, to cover very large page numbers(to ensure all component look and work fine with those values).
Screenshots
Screenshot showing parameters to be passed to paginator to recreate.
Clicking gotoPage dropdown/select will make the issue observable.
Additional context In one of our business use case, we want to display data in UI, which could have on an average few 100k records and sometimes upto few millions of records. The data is displayed in a table, so client side pagination is not done. Paginator is used to trigger API calls to fetch data with server side pagination. But number of pages is very large, UI becoming unresponsive and slowing down the page, causes issue.
Labels DxcPaginator, Largedataset, boundary condition
Thank you for opening an issue! 🚀
Our team will review it as soon as possible. In the meantime, please make sure that you've provided all the necessary details to help us understand and address the issue effectively.
Feel free to contribute and participate in discussions!
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue is stale because it has been open for 15 days with no activity. If there are no further updates or modifications within the next 15 days, it will be automatically closed.
This issue has been closed as it has been inactive for 15 days since being marked as stale.
This issue is stale because it has been open for 15 days with no activity. If there are no further updates or modifications within the next 15 days, it will be automatically closed.
