Files
web-at-transit/frontend
Bkk1234 7652ddaae5 stops: move the near-me result panel inside its own tab panel
The result container had been left outside #stops-near-wrap and an earlier
selout removed the wrong copy, so on /stops the map and ranked stops were
rendered at the bottom of the page instead of inside the third tab, unlike
the mock at :8090/ui/#/stops.

Now the DOM matches the mock exactly: three tabs, three panels, the location
button and its result inside the near panel, and only Search/Clear/Back in
the toolbar.

Compared side by side against :8090/ui/#/stops - tab order, panel visibility,
active state, list visibility on the near tab, geolocation result (map plus
8 ranked stops), button re-enable and repeat press all identical.
2026-10-24 00:20:12 +07:00
..
2026-05-24 22:55:17 +07:00
2026-05-24 22:55:17 +07:00
2026-05-24 22:55:17 +07:00
2026-05-24 22:55:17 +07:00
2026-05-24 22:55:17 +07:00
2026-05-24 22:55:17 +07:00
2026-05-24 22:55:17 +07:00

Frontend — Next.js App Router

npm install
npm run dev

Talks to backend purely via REST through nginx (/api/*, /files/*).