ux(map): place search with autocomplete flies the map #1192
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/place-search-ui"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Adds place search to the
/mappage by reusing the existing topbar search input. Typing two or more characters in the shared header field offers debounced gazetteer suggestions anchored directly under it; picking one flies the map to that place. This is a scope change from the earlier revision: the map-local overlay field is dropped and the suggestion UI now lives inside the header search.UX
/searchmedia submit unchanged, so the field still behaves as a media search everywhere.Design
AppHeadergains a single optionalonPlaceSearchSelectprop. When present the input becomes a combobox and the suggestion list mounts; when absent (every other page) the input is byte-for-byte the plain media-search box it was before.AppHeaderthrough a newpageHeaderPlaceSearchstore inpageMenu.ts, following the same pattern as the existingpageHeaderFilterSlot. The map page registers the fly handler on mount and clears it on destroy.TopbarPlaceSuggestions.svelteowns the debounced lookup, ARIA wiring, keyboard handling, and quiet states. It renders nothing until there is a real query, so non-map pages' header markup is untouched.placeSearch.tsclient and the existing fly logic are unchanged. TheMapViewoverlay slot and the oldMapPlaceSearchcomponent are removed.Testing