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.tsx supplies dashboard page URLs to PaginationLink, PaginationNext, and PaginationPrevious.
- The shared
PaginationLink renders 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?
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
/dashboard/caps.Additional Context
ghcr.io/capsoftware/cap-web:latest, confirmed against the published image on September 17, 2026.The current source appears to explain the behavior:
CapPagination.tsxsupplies dashboard page URLs toPaginationLink,PaginationNext, andPaginationPrevious.PaginationLinkrenders an ordinary<a>element rather than using Next.js client-side navigation.Could dashboard pagination use Next.js
Linkor equivalent client-side routing so changing pages does not reload the entire app?