FMP-CATALOG-001 · Application reliability · Repaired

When broken suggestions stop a typed search

Malformed occupation suggestions disabled typed search. The repair validates the optional catalog before replacing it, so typing remains usable.

Owned local code, fictional data and fresh profiles. This finding does not establish a browser-engine flaw, attacker access, customer losses or incident frequency.

What failed, and what had to be true

A fresh My People page received a malformed occupation catalog. The page said suggestions were unavailable and that a service could still be typed, but typing or submitting then failed before a search request was made. A valid catalog and a valid empty catalog each allowed one fictional search and one visible result. [1]

The browser receives an unexpected catalog shape, such as an object instead of an array, a null member or object-valued aliases. The test intercepts a response locally; it does not establish that a visitor or attacker can alter the production catalog.

Transition traced: Receive → parse → commit categories → later input uses the committed value → exception. The fallback message did not undo the earlier assignment.

Repair the boundary before committing state

Read the response within a 1 MiB byte limit, validate and detach the full catalog, and prepare its controls before committing it. Reject malformed or oversized suggestions while retaining the usable category state. A valid empty catalog remains a supported state, so typed search still works.

The unchanged-source run covered eight catalog shapes in each engine. Positive controls were a valid catalog and a valid empty catalog. Repaired cases require a completed typed search and no uncaught page error. Unit checks also exercise the actual 1,027-entry catalog, duplicate slugs, UTF-8 byte limits and cancellation of oversized streams. [1]

The browser repair ships in My People Release 6.

Use controls, not a dramatic payload

  1. Open an authorized local copy in a fresh profile with a fictional catalog and one fictional search result.
  2. Compare valid, empty and malformed catalogs before typing the same service and ZIP.
  3. Observe whether a search request is made, whether its result appears and whether the fallback message describes real behavior.
  4. Repeat the typed-search controls on repaired code. Separately run a bounded stream regression that exceeds the byte limit; that additional boundary was checked in a unit test.

Use synthetic records and an authorized local copy. Keep original failed receipts and distinguish a test-harness mistake from a product defect.

Evidence and limits

Reproduction and repair checks used Microsoft Edge 157.0.4341.46 and Playwright WebKit 26.5 on Windows. Physical Safari, iPhone, Android, native mobile keyboards and Firefox were not tested. Viewport checks do not establish physical-device behavior.

No malformed request was sent to production. The evidence shows the tested inputs and transitions; passing controls do not establish universal safety or account isolation.

[1] Original application evidence. See Browser Busters evidence, finding FMP-CATALOG-001. Exact baseline and repaired hashes, bounded private reproducers, browser receipts and failures remain in the project’s operational records. The public evidence contains no customer records or working attack code.