fix(map): avoid mobile pin-selection flicker by replacing ?select via history API

[badjoke-lab]

Motivation

• Pin taps on mobile caused visual flicker because router.replace triggered router-driven updates; the goal is to stop the flicker while preserving deep-linking for ?select= without touching Next Router behavior.

Description

• Add replaceSelectParam(placeId: string | null) which updates only the select query using new URL(window.location.href) and window.history.replaceState to avoid router navigation.
• Stop syncing selectedPlaceId via router.replace by removing the effect that performed router-based updates and leave the deep-link restoration from searchParams.get("select") intact.
• Call replaceSelectParam(placeId) from openDrawerForPlace and replaceSelectParam(null) from closeDrawer so URL reflects user actions without causing re-render flicker.
• Adjust the existing guard (skipNextSelectionRef) minimally to prevent an immediate double-update after user-triggered URL writes.

Testing

• Ran npm run -s lint -- components/map/MapClient.tsx which failed due to next lint requiring a pages/app directory in this environment (lint did not validate the change here).
• Ran npm run -s test:stats which reported unrelated repository test failures (Cannot find module '@/lib/db') so full test suite could not be validated end-to-end.
• Ran npx tsc --noEmit which produced unrelated type/fixture errors in test files, so typecheck could not be fully validated in this CI-like environment.

---

Codex Task

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
cryptopaymap-v2	Ready	Preview, Comment	Feb 22, 2026 8:56am