Skip to content

feat(material/paginator): Allow user to directly navigate to specific page using field Goto: #27186

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
nishchay7pixels opened this issue May 27, 2023 · 2 comments
Labels
feature This issue represents a new feature or feature request rather than a bug or bug fix needs triage This issue needs to be triaged by the team

Comments

@nishchay7pixels
Copy link
Contributor

Feature Description

I see there is a this respective Issue still open: bug(table): Table data does not get updated when paginator pageIndex is modified #26890

Not sure if anyone still working on it.

But I propose that will it not be better to have a dropdown like 'Items per page:' that says 'Goto:' which allow user to directly select a page from dropdown or an input field that let user enter the exact page index they want to land on.

Something like below.
image

Just like Items Per Page, Got page dropdown will also be controlled by a boolean flag which if enabled will display it as part of paginator and if disabled will hide it.

Use Case

In case of hundreds of records which leads to a lot of pages, this will will allow user to directly navigate to the page that interest them. This can be some page they found have information that they might need while they are scrolling through all the pages and once they are done with all the pages they can directly goto the pages they marked as relevant.

@nishchay7pixels nishchay7pixels added feature This issue represents a new feature or feature request rather than a bug or bug fix needs triage This issue needs to be triaged by the team labels May 27, 2023
@crisbeto
Copy link
Member

Duplicate of #7615.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature This issue represents a new feature or feature request rather than a bug or bug fix needs triage This issue needs to be triaged by the team
Projects
None yet
Development

No branches or pull requests

2 participants