You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, in the flowbite-svelte pagination component, a user will always see previous / next buttons regardless of what the active page is. This may not be desired if the user is on the first or last page.
This is how things look right now. I would put the entire <li> into the slot, so that a user can optionally define empty slots to represent no back or forward buttons.
Motivation
This is the way that many pagination components work on the web. And if they do not work this way, they at least have a disabled mouse icon on the previous button (which currently does not happen).
So, moving around the PaginationItem is probably a good idea anyway, because it allows for greater customization than of just the text / icon; this way you'd be able to e.g. change the entire background of the item by using a custom PaginationItem.
The text was updated successfully, but these errors were encountered:
Summary
Currently, in the
flowbite-svelte pagination
component, a user will always see previous / next buttons regardless of what the active page is. This may not be desired if the user is on the first or last page.Basic example
This is how things look right now. I would put the entire
<li>
into the slot, so that a user can optionally define empty slots to represent no back or forward buttons.Motivation
This is the way that many pagination components work on the web. And if they do not work this way, they at least have a disabled mouse icon on the previous button (which currently does not happen).
So, moving around the PaginationItem is probably a good idea anyway, because it allows for greater customization than of just the text / icon; this way you'd be able to e.g. change the entire background of the item by using a custom PaginationItem.
The text was updated successfully, but these errors were encountered: