Rows per page
Rows per page is a Pagination block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
The other half of paging: how many rows a page is, before which page you are on
Anatomy
Grey track, the chosen size lifted onto a sliding white thumb · only the chosen one says rows · the range said in full under it
Showing 1–20 of 248 results
In the Orvain Library
Get Rows per page for your product
The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.
- React
- Vue
- Figma frame
- Orvain MCP
About this block
Part of Pagination
What’s inside
03parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
- Grey trackthe chosen size lifted onto a sliding white thumb
- Only the chosen one says rows
- The range saidin full under it
Responsive behaviour
480 px
Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.
When to use it
Where Pagination earns its place
Reach for Pagination
- A result set long enough that people jump to a page rather than scroll to one.
- Under a table, where the reader also has to choose how many rows a page is.
- Queries paged on the server, where a page is a request rather than a slice of something already loaded.
- A position that has to survive a reload, a shared link or a colleague reading it out.
Reach for something else
- A feed read in order with no particular destination: a Load more button or continuous scrolling matches how people actually move through it.
- Records that shift position while the set is being read: a cursor anchored to the last record seen beats page numbers that renumber underneath the reader.
- A set that fits on one screen: show all of it; a pager under a list that was never going to be cut is a control with nothing to do.
Accessibility
06to keep
What the block ships with. Hold on to these as you make it yours.
- Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
- Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
- More than colourA state never rides on colour alone; a mark or a word goes with it.
- Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
- Calm motionFor visitors who ask for reduced motion, things simply appear.
- Room to hitTargets stay at least 24px, with space between neighbours.
Notes for AI
1 line
Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.
Add the Orvain “Rows per page” block to this page: grey track, the chosen size lifted onto a sliding white thumb, only the chosen one says rows, the range said in full under it.
Questions about Rows per page.
What is the Rows per page block?
Rows per page is a Pagination block from Orvain UI, built for React and Vue with a matching Figma frame. Best for the other half of paging: how many rows a page is, before which page you are on.
What is the Rows per page block made of?
3 parts: grey track, the chosen size lifted onto a sliding white thumb; only the chosen one says rows; and the range said in full under it. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Is the Rows per page block responsive?
Yes. It is drawn at 480px and never stretched past that. Below it, its controls, text and spacing step down with the container the block sits in rather than the browser window, so it holds up in a sidebar, a tablet layout and a 390px phone without clipping or sideways scrolling.
Is the Rows per page block accessible?
It ships with text labels on every icon-only button, full keyboard reach with a visible focus ring, states that never rely on colour alone, text contrast that holds when you retheme it, no animation for visitors who ask for reduced motion, and click targets of at least 24px.
How do I add the Rows per page block to my project?
It is part of every Orvain Library plan: the React and Vue code, its frame in the Orvain Figma file, and the Orvain MCP server. With the MCP connected, an AI assistant such as Claude Code, Cursor or v0 can build it from one line: “Add the Orvain Rows per page block to this page.”
When should I not use a Pagination block?
A feed read in order with no particular destination: a Load more button or continuous scrolling matches how people actually move through it.
More Pagination blocks
All PaginationPremium components,
free in your inbox.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Orvain MCPRows per page
Rows per page is a Pagination block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
The other half of paging: how many rows a page is, before which page you are on
Anatomy
Grey track, the chosen size lifted onto a sliding white thumb · only the chosen one says rows · the range said in full under it
Showing 1–20 of 248 results
In the Orvain Library
Get Rows per page for your product
The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.
- React
- Vue
- Figma frame
- Orvain MCP
About this block
Part of Pagination
What’s inside
03parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
- Grey trackthe chosen size lifted onto a sliding white thumb
- Only the chosen one says rows
- The range saidin full under it
Responsive behaviour
480 px
Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.
When to use it
Where Pagination earns its place
Reach for Pagination
- A result set long enough that people jump to a page rather than scroll to one.
- Under a table, where the reader also has to choose how many rows a page is.
- Queries paged on the server, where a page is a request rather than a slice of something already loaded.
- A position that has to survive a reload, a shared link or a colleague reading it out.
Reach for something else
- A feed read in order with no particular destination: a Load more button or continuous scrolling matches how people actually move through it.
- Records that shift position while the set is being read: a cursor anchored to the last record seen beats page numbers that renumber underneath the reader.
- A set that fits on one screen: show all of it; a pager under a list that was never going to be cut is a control with nothing to do.
Accessibility
06to keep
What the block ships with. Hold on to these as you make it yours.
- Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
- Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
- More than colourA state never rides on colour alone; a mark or a word goes with it.
- Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
- Calm motionFor visitors who ask for reduced motion, things simply appear.
- Room to hitTargets stay at least 24px, with space between neighbours.
Notes for AI
1 line
Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.
Add the Orvain “Rows per page” block to this page: grey track, the chosen size lifted onto a sliding white thumb, only the chosen one says rows, the range said in full under it.
Questions about Rows per page.
What is the Rows per page block?
Rows per page is a Pagination block from Orvain UI, built for React and Vue with a matching Figma frame. Best for the other half of paging: how many rows a page is, before which page you are on.
What is the Rows per page block made of?
3 parts: grey track, the chosen size lifted onto a sliding white thumb; only the chosen one says rows; and the range said in full under it. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Is the Rows per page block responsive?
Yes. It is drawn at 480px and never stretched past that. Below it, its controls, text and spacing step down with the container the block sits in rather than the browser window, so it holds up in a sidebar, a tablet layout and a 390px phone without clipping or sideways scrolling.
Is the Rows per page block accessible?
It ships with text labels on every icon-only button, full keyboard reach with a visible focus ring, states that never rely on colour alone, text contrast that holds when you retheme it, no animation for visitors who ask for reduced motion, and click targets of at least 24px.
How do I add the Rows per page block to my project?
It is part of every Orvain Library plan: the React and Vue code, its frame in the Orvain Figma file, and the Orvain MCP server. With the MCP connected, an AI assistant such as Claude Code, Cursor or v0 can build it from one line: “Add the Orvain Rows per page block to this page.”
When should I not use a Pagination block?
A feed read in order with no particular destination: a Load more button or continuous scrolling matches how people actually move through it.
More Pagination blocks
All PaginationPremium components, free in your inbox.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
