NLS search field — current variants

Review surface for #2503, the search / quick-search half: where the NLS field is used and what it looks like in each layout it already supports. Current behaviour only — nothing here is a proposed design yet.

#2503 places NLS on stand-alone search-form and quick-search widgets, and not on Results / Map headers. Action-plan item 3 is the roll-out to quicksearch via formType:simple2. The cases below show what that token does today on the NLS widget, and what QuickSearch renders in the same slot, so the two can be compared directly.


1 — NLS search form, default

Full pill toolbar. This is what the stand-alone SearchFormNLS widget renders with no layout tokens.

SearchFormNLS — no data-filter

2 — NLS search form, formType:simple2

Adds .nls-simple, which hides the filter pills and leaves a single input plus a magnifying-glass submit. The NLS parsing is unchanged — typed text still extracts price, beds, baths and so on.

SearchFormNLS — formType:simple2

3 — NLS search form, formType:simple2 + formLayout:rounded

Adds .nls-rounded on top: white background, large corner radius, circular submit button.

SearchFormNLS — formType:simple2 + formLayout:rounded

4 — QuickSearch, for comparison

What sits in that slot today. simple1 is the QuickSearch default; simple2 is the token NLS reuses, so the two widgets are meant to be swappable with one attribute change.

QuickSearch — formType:simple1 (default)
QuickSearch — formType:simple2
QuickSearch — formType:simple2 + formLayout:rounded

5 — In a narrow slot (420px)

Quick-search usually sits in a hero band or a sidebar rather than full width. Same two widgets, same tokens, constrained — the widget sizes from its container, so this is the case that actually matters.

SearchFormNLS — simple2 + rounded, 420px
QuickSearch — simple2 + rounded, 420px