Dashboard pagination causes full page reloads on self-hosted Cap
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- nextjs, typescript
Research direction
Start by reading apps/web/app/(org)/dashboard/caps/components/CapPagination.tsx and packages/ui/src/components/Pagination.tsx, then reproduce the behavior at /dashboard/caps. Update pagination navigation so page changes keep the dashboard shell mounted, and verify that page-number and Next/Previous clicks no longer cause a full page reload.
Written by the indexing model from the issue text.
Description
Description
While testing a migration from Loom to self-hosted Cap, I noticed that pagination in the My Caps dashboard triggers a full page/app reload on every page change. This makes browsing a large video library feel sluggish.
Expected: pagination updates the video list using client-side navigation, keeping the dashboard shell mounted.
Actual: clicking a page number or Next/Previous reloads the whole page.
Reproduction
- Open a self-hosted Cap Web instance and sign in.
- Have enough recordings in My Caps to display pagination.
- Navigate to
/dashboard/caps. - Click the next page number or Next/Previous.
- Observe a full page reload rather than an in-app transition.
Additional Context
- Cap version:
ghcr.io/capsoftware/cap-web:latest, confirmed against the published image on September 17, 2026. - Image build date: September 7, 2026.
The current source appears to explain the behavior:
CapPagination.tsxsupplies dashboard page URLs toPaginationLink,PaginationNext, andPaginationPrevious.- The shared
PaginationLinkrenders an ordinary<a>element rather than using Next.js client-side navigation.
Could dashboard pagination use Next.js Link or equivalent client-side routing so changing pages does not reload the entire app?
- Dominant language
- Rust
- Stars
- 22.5k
- Forks
- 1.9k
- Avg merge
- 6h 33m
- Merged PRs (30d)
- 77
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CapSoftware/Cap
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CapSoftware/Cap#1714 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 67/100
CapSoftware/Cap#2324 · 1 comment ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 38/100
CapSoftware/Cap#2323 · 1 comment ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
CapSoftware/Cap#2311 · 2 comments ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
CapSoftware/Cap#2310 · 2 comments ·
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bitcoindevkit/bdk-ffi#1125 ·