Navigation buttons in the vs-pagination component should disable
#300
Comments
|
If the above is agreeable, I am willing to help out with implementing this. |
|
@jacrys Great is very successful you can help making a PR on this |
luisDanielRoviraContreras
added a commit
that referenced
this issue
Oct 16, 2018
Fix #300 - Correct Pagination Nav Buttons
Tofandel
pushed a commit
to Tofandel/fixed-vuesax
that referenced
this issue
Apr 26, 2021
Fix the next and previous buttons in pagination to disable them upon hitting max pages and min pages respectively. Also changed cursor on the disabled and active items for pagination to use the default cursor, falling closer in line with web standards, Fixes lusaxweb#300
Tofandel
pushed a commit
to Tofandel/fixed-vuesax
that referenced
this issue
Apr 26, 2021
Fix lusaxweb#300 - Correct Pagination Nav Buttons
Tofandel
pushed a commit
to Tofandel/fixed-vuesax
that referenced
this issue
Apr 26, 2021
Fix the next and previous buttons in pagination to disable them upon hitting max pages and min pages respectively. Also changed cursor on the disabled and active items for pagination to use the default cursor, falling closer in line with web standards, Fixes lusaxweb#300
Tofandel
pushed a commit
to Tofandel/fixed-vuesax
that referenced
this issue
Apr 26, 2021
Fix lusaxweb#300 - Correct Pagination Nav Buttons
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The next/prev buttons on the
vs-paginationcomponent should disable after reaching max/min page respectively. This brings the component in line with other pagination components and closer to expected and accepted behaviour for this class of component.The text was updated successfully, but these errors were encountered: