Record nav arrows

Previous / next record in the top bar of a detail opened from a list, followed by the position „Plocha · n/m". RecordNavArrows (apps/web/src/components/RecordNavArrows.tsx) on person, company, deal, meeting, project and the mail reader (komunikace/MessagePage.tsx). Owner approval 11 Oct 2026 (R47, R48; acrm !4962, prototype proto/record-nav-arrows@5f98c373d).

When to use

• A detail opened from a list that carries the list context in the router state (which list, which position).

When not to use

• A detail opened from a link, search or a notification — there is no list to walk; the arrows and the position are not drawn at all.
• Paging inside one list (that is the list's own pager).

Anatomy

1. ↑ Previous · ↓ Next — two quiet IconButtons side by side, title „Předchozí (K)" / „Další (J)". Disabled at the ends.
2. Position „Doručené · 2/50" / „Lidé · 3/159" (.tbar-pos) after the arrows. When the list route is known it is a link back to the list (.tbar-pos.is-link) — the same as Esc / back.
3. Keys J (next) and K (previous); ignored while typing in a field or when an overlay is open.
4. Phone (≤ 720 px): no arrows (swipe-free, R48); the position link stays in the record header as the way back, because the phone has no ✕.

Best practices

Do

• One order everywhere: ↑ ↓ then the position — records and the mail reader alike.
• Name the surface in the position („Doručené", „Lidé"), not just n/m.

Don't

• No own arrow markup per screen (the mail reader had km-nav-btn with ↑ n/m ↓ until !4962).
• No arrows on the phone.

Content

„<Plocha> · n/m" — the surface name as in the sidebar, a middle dot, position over total.

Related

Section top bar · Record actions menu · Icon button