FA-24114 / Client state / Member archive

Page freeze and resume lifecycle: Dirty pagehide flush · case 04

Dirty pagehide flush.

Member previewVariant 4 · 3 implementations · 60 checks per implementation

Case contract

The stipulated page lifecycle distinguishes a cached pagehide from final disposal. Timers pause on hide/freeze, dirty snapshots flush on any pagehide, and resume/pageshow may revalidate and drain retained work. Operation dirty-pagehide-flush has the six explicit input/output oracles below.

Why this case matters

An offline client lifecycle model that isolates a state-management defect without DOM rendering or network services.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
dirty-pagehide-flush scenario 5	`true`	`false`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.