checking which build is live…

Area search header — #2503 review rig

One widget, deliberately. data-filter="searchType:area" with no formType, which resolves to form-header.phtml — the header this issue rebuilt. Resize the window to check narrower layouts.

The bundle is the preview-branch build from CI (see the banner at the top of the page), not a hand-uploaded file and not a per-PR object — see the comment in the page source for why a per-PR pin breaks on merge. The CSS comes from preview's own theme build; the two /src/*-delta.css sheets layered on top are legacy and due to go.

ListingResults — area-search header, RESIZABLE
container fitpx set widget sees —px — or drag the green grip on the right edge

Widths that should change something, from the container queries in _searchform.scss — 1040 Status goes, 940 Home type goes, 768 the row splits in two with the menu and Save Search above. Below roughly 600 an older rule takes over and hides the whole row behind Show Filters, so the spec's last two steps (drop Beds & Baths, then Price) cannot be seen here yet — a known gap, not this page misbehaving.
"widget sees" is the number that matters. It is the widget's own resolved width, which is what @container reads; the box you drag is 24px wider because of its 10px padding and 2px border.


Notes — read this before changing anything

This page is the ONLY review surface for #2503. It had sixteen widgets (a width series at 1200/900/768/600/480/360 for both SearchForm and ListingResults, plus two QuickSearch). They were removed 2026-09-25: preview rate-limited the render calls (429 bursts, widgets coming up empty), and having many near-identical rigs made it easy to measure one and report on another. Do not add rigs back without a reason.

formType decides which header file renders, and it is the thing that caused the most confusion. FORM_TYPES in BlueFire/Widget/Registry.php:

What this release added to form-header.phtml, each a partial plus a self-upgrading component, because in the NLS toolbar these only ever worked through MbbSearchFormNLS and a host of MbbSearchForm wires none of it:

Three traps that each cost a round, all live in code this page exercises:

  1. MbbSearchClass.initFilterPills() calls stopPropagation() on every .nls-dropdown click, which kills any delegated listener above the dropdown. It has eaten three handlers. Bind inside the dropdown, not on the component.
  2. initAdvancedSearch() binds the legacy full-screen modal to .MoreFiltersWrapper button. The MORE panel lives in that same cell, so the modal used to steal its click — and its preventDefault also cancelled the popover. Guarded on mbb-search-more-panel.
  3. A capability on MbbSearchClass is worthless until a host CALLS it. Four controls arrived here present, styled and completely inert for exactly this reason, with no console error.
  4. A control that moves itself to document.body leaves the stylesheet behind. Every .nls-* rule is scoped to [id*='_SearchForm' i] and its three siblings, so a node appended outside the widget container gets none of them — and if it also lives in its own shadow root, Bootstrap's .dropdown-menu/.show pair has to be inside that root too. This is what made the old mbb-propertytype-menu flip aria-expanded and show nothing. The MORE panel escapes the container legitimately only because it is a popover, which the browser paints in the top layer.

THE ROW SPEC — Tadd, 2026-09-25. This is the target; check work against it.

Container ≥ 768px — ONE row:

[ menu ] [ Area/NLS ..... ] [ Status ] [ Price ] [ Beds / Baths ] [ Home type ] [ MORE ] [ VIEW ] [ SAVE SEARCH ]

As it narrows, controls DROP in this order, still one row:

hide [ Status ]     → [ menu ] [ Area/NLS ..... ] [ Price ] [ Beds / Baths ] [ Home type ] [ MORE ] [ VIEW ] [ SAVE SEARCH ]
hide [ Home type ]  → [ menu ] [ Area/NLS ..... ] [ Price ] [ Beds / Baths ] [ MORE ] [ VIEW ] [ SAVE SEARCH ]

Container < 768px — TWO rows. [ menu ] and [ SAVE SEARCH ] move to a row ABOVE:

[ menu ] [ SAVE SEARCH ]
[ Area/NLS ..... ] [ Price ] [ Beds / Baths ] [ MORE ] [ VIEW ]

Then the dropping continues:

hide [ Beds / Baths ] → [ Area/NLS ..... ] [ Price ] [ MORE ] [ VIEW ]
hide [ Price ]        → [ Area/NLS ..... ] [ MORE ] [ VIEW ]

Full drop priority: Status → Home type → (at <768px, menu + Save Search move up) → Beds / Baths → Price. Area/NLS, MORE and VIEW never drop.

There is exactly ONE menu and ONE Save Search. inc-row1.phtml used to render both in a row above on results mounts and is no longer included at all — it contained nothing else. If you see two of either, that partial has come back.

How a change actually reaches this page — three different channels:

Consequence: a change spanning all three shows up PARTIALLY until the merge, which looks like a broken half-state rather than work in progress. Check which channel a thing lives in before concluding it is broken.

Still to do:

Done since this note was last touched: the area-search input (prepend icon removed, 40px tall, 4px corners), Save Search (one instance, on the same row, no icon, identical to VIEW), and Home type (was mbb-propertytype-menu, now the pill — see the fourth trap above for why the old one was invisible).