UA Ledger · Playable Test Bench · draft for review
Teaching laboratory. Cases run in this page against the authored functions. This is not a device panel, network approval, analytics-delivery proof or campaign result. Inputs are synthetic.
Restarting a playable while an earlier load is still pending can let stale data overwrite the new session. This fixture tests an explicit generation boundary around accepted results.
Primary documentation: MDN: stale load (body read 2026-09-19).
| Case | Input | Expected | Fixed | Broken |
|---|
A pass proves that a late old-generation response cannot win in the supplied sequence. It does not demonstrate that a real request was cancelled, that all dependent work stops, or that an older response cannot leak resources. Those are additional integration checks for the actual asynchronous pipeline.