fix: use document.referrer for reliable back navigation

[mitoperni]

Description

Replace unreliable window.history.length check with document.referrer origin comparison for the back button in network detail pages. history.length counts all browser history entries (not just the app's), so router.back() could navigate outside the app when users arrive from external links like Google search results.

Type of Change

• New feature
• Bug fix
• Refactoring
• Documentation
• Styling

Changes Made

• src/components/stations/stations-header.tsx: Replace window.history.length > 1 with document.referrer same-origin check. If the user navigated from within the app, router.back() preserves URL filters. If from external, router.push('/') safely redirects to home.

Screenshots (if applicable)

N/A

Checklist

• Code follows project style guidelines
• Self-review completed
• No TypeScript errors
• Tests added/updated
• All CI checks pass
• Tested on different screen sizes
• Loading states implemented
• Error handling in place

Related Issues

N/A

---

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
cyclemap	Ready	Preview, Comment	Feb 9, 2026 6:49pm

[devin-ai-integration]

Devin Review found 1 potential issue.

View 3 additional findings in Devin Review.

[mitoperni]

Superseded by #62. The document.referrer approach doesn't work for client-side (SPA) navigations in Next.js since it's only updated on full page loads. The new PR uses sessionStorage to track the previous path, which works reliably for both SPA and full-page navigations while also preserving filter/search params.