[DxcPaginator] Paginator select becomes unresponsive when number of pages is too large #2220
Description
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