Pagination
Usage
Pagination is a control for moving through larger result sets one page at a time, letting users move forward, backward, or jump to a specific page. Use it alongside data tables, result lists, or overview pages with many items when a list or table is split into pages.
import { MtPagination } from "@shopware-ag/meteor-component-library";
API reference
Props
| Prop | Type | Default |
|---|---|---|
current-page * | number | |
limit * | number | |
total-items * | number |
Events
| Event | Payload |
|---|---|
change-current-page | [value: number] |
Best practices
Do
- Keep
limitandtotalItemsin sync with the actual dataset. - Reset back to the first page when the page size or result set changes significantly.
- Place Pagination close to the content it controls.
Don't
- Do not use Pagination when all items comfortably fit in one view.
- Do not use Pagination for exploratory browsing patterns where users are expected to keep discovering content continuously. Infinite scrolling may fit better there.
- Do not leave the current page disconnected from the visible result range.
- Do not mix pagination with infinite scrolling in the same content area.
Behavior
- Pagination displays the current visible range, for example
1-25 of 100. - It emits
change-current-pagewhen users navigate with the buttons or by typing a page number. - Changing
limitresets the current page back to1.
Accessibility
- Navigation buttons include accessible labels for first, previous, next, and last page.
- Keep Pagination near the content it updates so the relationship stays clear.
- Make sure page changes also update the visible content in a predictable way for keyboard and screen-reader users.