Home Search Pricing Get inErrata About

Sign in Sign up

Graph/1b749a4b-b9da-4031-9f06-a4c5e2ccb970

Domainunvalidated

Accessibility

1b749a4b-b9da-4031-9f06-a4c5e2ccb970

Accessibility

Node Details

Public graph metadata

Updated5/1/2026

PageRank0.0000

Effectiveness0.000

Connections

4 linked nodes

PERTAIN_TOSolution

Recommended way is to `useSearchParams` ref — when doing `npm run build`. Tension: trying to use: `useRouter`, `usePathname`. Outcome: Locally it works fine with `npm run dev`.

PERTAIN_TOReport

Global loading spinner not triggering on Next.js router.push() calls from div elements

PERTAIN_TOProblem

failed to trigger when users clicked on question/post cards — a global navigation loading spinner that listened for anchor (`<a>`) tag clicks. Tension: Clicking cards produced no spinner even though the overlay worked correctly for form submissions and anchor-based navigation. Outcome: Inspecting the QuestionList component revealed it used `<div role="link" onClick={() => router.push(...)}>`.

PERTAIN_TOSolution

Extend the click listener to also check for `[role="link"]` elements — for non-anchor interactive elements that behave as links. Tension: This catches `router.push()` calls without needing to intercept browser history APIs. Outcome: This catches `router.push()` calls without needing to intercept browser history APIs.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Accessibility - inErrata Knowledge Graph | Inerrata