FMP-RESTORE-001 · Application reliability · Repaired

Recovering a saved list without overwriting it

Malformed saved records interrupted startup and restoration. Recovery now preserves original storage, usable entries and the last valid cross-tab view.

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 synthetic saved list contained one valid person and a second record with a numeric phone or object-shaped listing type. Both records passed the old basic identity check. Rendering stopped after one card, while the saved count showed two; startup navigation did not initialize. A malformed cross-tab replacement and a pre-existing malformed history entry also interrupted restoration. Original local-storage bytes were not deleted. [1]

Malformed data must already be present in this browser’s saved list, arrive through its storage event, or exist in a history entry. The tests seed fictional local state. No remote path for altering a visitor’s storage or history was demonstrated.

Transition traced: Read or restore → basic id/name check → commit saved/history state → render optional fields → exception. Validating only identity did not establish that the record could be rendered.

Repair the boundary before committing state

Use a shared listing contract before rendering or restoring. At startup, show usable recovered entries while retaining the original storage bytes. Pause mutations when recovery is needed; explicitly clearing the entire saved list is a deliberate reset. Reject a malformed cross-tab replacement before changing the committed in-tab list. Reject malformed history snapshots before applying them. A storage event does not undo another tab’s write: the repair preserves this tab’s committed view, not an atomic cross-tab transaction. A storage event does not undo another tab’s write: the repair preserves this tab’s committed view, not an atomic cross-tab transaction.

Valid and empty stored lists remain usable. Repaired checks cover mixed and all-invalid records, preservation of raw storage, blocked implicit overwrites, explicit clearing, cross-tab rejection, malformed history and ordinary filters with Back, Forward and refresh. These are local-state recovery checks, not account authorization tests. [1]

The browser repair ships in My People Release 6.

Use controls, not a dramatic payload

  1. Seed a fresh local profile with two fictional saved records; change only an optional text field in one record to the wrong type.
  2. Reload and compare the count, visible cards, storage bytes and navigation readiness with a valid-list control.
  3. From a second local tab, replace storage with a malformed candidate and observe the first tab’s committed list.
  4. Verify repaired recovery, a deliberately confirmed clear, and ordinary history navigation without seeding malformed data.

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-RESTORE-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.