[jay23606]

Problem

Clicking a cluster, locating yourself, selecting a pin or choosing a city all called Leaflet's animated flyTo / flyToBounds, and the map's zoom, fade and marker-zoom animations were always on. Visitors with prefers-reduced-motion: reduce still got long animated pans and zooms, which can trigger vestibular symptoms. Only the hero particles honoured the setting.

Change

• map-view.tsx: a small prefersReducedMotion() helper (guarded for SSR and environments without matchMedia).
• The five flyTo / flyToBounds calls (cluster click, cluster keydown, FlyToUser, FlyToPlace, FlyToBounds) pass animate: !prefersReducedMotion(), read at call time.
• MapContainer gets zoomAnimation, fadeAnimation and markerZoomAnimation set from the same check.

With the setting off, the options are animate: true, which is Leaflet's default, so the animations are unchanged.

Testing

• Added one regression test in src/components/map/map-view.test.tsx: it stubs matchMedia to match (prefers-reduced-motion: reduce) and asserts flyTo receives animate: false. It fails on the base code with expected "vi.fn()" to be called with arguments and passes with the change.
• npm run test:unit passes (580 tests).
• npm run lint and npx tsc --noEmit pass.
• Prettier passes for the two changed files (npx prettier --check --end-of-line crlf ...).

Not verified in a browser with devtools emulation; the unit test covers the call options only.

Refs #297

Regression test: fails on base twice (/to be called with arguments/), passes on fix twice (npx vitest run src/components/map/map-view.test.tsx -t "prefers-reduced-motion")

Fixes #297

[jay23606]

I have read the CLA Document and I hereby sign the CLA

[vercel]

@jay23606 is attempting to deploy a commit to the studentsuite Team on Vercel.

A member of the Team first needs to authorize it.