We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Method - 1 I was thinking of hiding prev / next button using if else based on currentPage and totalPages.
Method - 2 Adding css to make it look like a disable button and not invoking setQueryParams().
It shouldn't flicker
Windows
Chrome
No response
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered:
@VineeTagarwaL-code should I work upon it ?
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
📜 Description
👟 Reproduction steps
Method - 1
I was thinking of hiding prev / next button using if else based on currentPage and totalPages.
Method - 2
Adding css to make it look like a disable button and not invoking setQueryParams().
👍 Expected behavior
It shouldn't flicker
👎 Actual Behavior with Screenshots
100xJobs.-.Google.Chrome.2024-11-04.20-06-17.mp4
OS name
Windows
browser name
Chrome
npm version
No response
node version
No response
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Contributing Guidelines?
Are you willing to submit PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: