Skip to content
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

unstable_Pagination does not fire onChange for next and previous buttons #1051

Closed
tusharcoepit opened this issue Jul 22, 2021 · 5 comments
Closed
Labels
status: triage type: bug Something isn't working wontfix This will not be worked on

Comments

@tusharcoepit
Copy link

tusharcoepit commented Jul 22, 2021

Pagination component has a performance issue when data is huge.

#162

As an alternative we are trying to use unstable_Pagination, but it does not trigger onChange on click of next and previous buttons.

Any other alternatives to handle the performance issue with Pagination is also welcome.

We are on "@carbon/ibm-security": "1.41.0",

@tusharcoepit tusharcoepit added status: triage type: bug Something isn't working labels Jul 22, 2021
@SimonFinney
Copy link
Contributor

Thanks @tusharcoepit - are you leveraging the component per the example story in the Carbon repo?

@tusharcoepit
Copy link
Author

Yes @SimonFinney, we are referencing the storybook. In-fact on story book as well we don't see onChange event triggering for next / previous buttons and it triggers only on page selection from dropdown.

We are referring this -> https://react.carbondesignsystem.com/?path=/story/experimental-unstable-pagination--with-a-page-selector

@SimonFinney
Copy link
Contributor

Yes @SimonFinney, we are referencing the storybook. In-fact on story book as well we don't see onChange event triggering for next / previous buttons and it triggers only on page selection from dropdown.

We are referring this -> https://react.carbondesignsystem.com/?path=/story/experimental-unstable-pagination--with-a-page-selector

Thanks for clarifying! I believe this issue should be created in Carbon as the component is proxied from there.

@tusharcoepit
Copy link
Author

Created issue in carbon carbon-design-system/carbon#9313

@stale
Copy link

stale bot commented Apr 16, 2022

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the wontfix This will not be worked on label Apr 16, 2022
@stale stale bot closed this as completed Apr 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: triage type: bug Something isn't working wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants