You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 15, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 15, 2026. It is now read-only.
Stop the onboarding border-trace rAF loop once settled #46
Currently, useBorderTrace runs a continuous requestAnimationFrame loop during onboarding (src/views/onboarding/useBorderTrace.tsx:112) that never stops re-scheduling, even once the trace is permanently held and the tint has settled. The hook is well engineered (guards redundant DOM writes, respects prefers-reduced-motion, cancels rAF on cleanup), but it keeps the main thread busy at idle. This is a minor problem because it burns frames after the animation has nothing left to do.
Expected outcome
The rAF loop stops re-scheduling once the trace is permanently held and the tint has settled, and resumes only if state changes again — preserving all current visual behavior and reduced-motion handling.
Acceptance criteria
The rAF loop stops re-scheduling once the trace is held and tint settled.
Existing guards (redundant DOM-write avoidance, prefers-reduced-motion, rAF cleanup on unmount) are preserved.
No visual regression in the onboarding border-trace animation.
Activity