Queue each History back/forward/go delta as its own authorized traversal task and resolve the destination when that task runs. Keep the committed traversal position separate from synchronous history mutations, and use the canonical Window history for isolated-world calls. Preserve Navigation API result-bearing traversal behavior.
Cover consecutive and opposite deltas, initially out-of-range requests, synchronous pushState, canceled and reentrant traversals, child documents, and isolated worlds. Update old coalescing assertions and wait for actual browser-owned history commits in protocol tests.
Validation: cargo fmt --all; cargo clippy --workspace --all-targets --all-features -- -D warnings; cargo nextest run --no-fail-fast (17584 passed, 13 skipped). Overlapping navigation WPT improves from 16/22 to 18/22, with both new cases passing all 8 subtests. Navigation API comparison preserves all 385 previously passing cases out of 432.
CDP smoke: 41/43 passed. The dom-input FileList upload failure reproduces on the parent binary; puppeteer could not start because Node is missing locally. Artifacts: target/wpt-history-traversal-20260908-lcpQpn/{before,confirmed,navigation-after,cdp,cdp-before}.
Retain each manually followed HTTP hop's request/response ExtraInfo and
derive redirect availability from observed exchanges instead of a fixed flag.
Keep wire ExtraInfo when interception changes the logical response, and
preserve buffered redirect metadata without announcing requests twice.
Cover Worker fetch/XHR through two 302 Set-Cookie hops, including synthetic
first-hop redirects that must not produce transport ExtraInfo.
Retain admission cookie metadata in the typed automation event for BiDi, while deferring CDP Cookie headers and ExtraInfo to observed transport data.
Verify a Service Worker supplied iframe script executes without an HTTP script request or invented CDP Cookie header, and keep the prepared metadata available to BiDi.
Keep repeated native request snapshots in the output queue so Fetch overrides refresh captured upload bodies. Mark which snapshots announce a new request and suppress duplicate CDP starts during metadata enrichment.
Check that chained binary, text and empty upload overrides preserve a single requestWillBeSent per request and session.
Prepare initial headers and cookie metadata through the child Document's
request client, including credentials and browser site-context policy.
BiDi beforeRequestSent and terminal events retain this request metadata.
Defer CDP ExtraInfo separately so admission cookie metadata does not consume
the single later transport ExtraInfo event. Test HTTP 200, HTTP 404 and
cross-origin anonymous script requests.
Use Document resource-load leases and shared cache consumer cancellation
for announced child parser scripts. Finish the original request on
retirement, ignore late callbacks, and publish completion independently
of parser-runner lifetime when navigation is cancelled.
Track request ExtraInfo publication separately from enriched cookie
metadata so HTTP-error responses preserve one Cookie ExtraInfo event.
Cover held-response retirement, cancelled srcdoc, late source callbacks,
and repeated metadata enrichment with regression tests.
Commit Browser detach and auto-attach disable synchronously, preserving event
ordering while supervising each native retirement independently. Remove the
synthetic completion objects, test-only serial runner, and obsolete recovery.
Batch script removal with SessionPageUpdates and retain the original disposal
identity for completion. Enqueue target-owned Inspector initialization without
claim/reply observers or a cancellable route. Share endpoint selection and
borrow connection keys/bindings separately from navigation restore snapshots.
Clarify session admission names and separate static policy from Page readiness
selection while retaining the admission token through synchronous redispatch.
Exercise the production Browser commit and supervisor paths in disposal tests.
Supervise each retired session independently so a busy Renderer cannot delay
another target's detach finalizer and successor connection. Preserve Browser
cascade publication and each session's cleanup-before-retirement ordering.
Apply Page subscriptions at command admission and defer only their initial
Document work. Resume without replaying an obsolete enable or chooser setting.
Remove the redundant cleanup owner and unreachable connection replacement.
Cover Primary lane reuse across auto-attach with a held peer, and Page
subscription changes while the initial installer remains pending.
Commit Browser attachment and withdrawal independently of native Page and
Inspector initialization. Keep shared initial builds on the target and bind
queued Main/IO work to its admitted session connection and native agent.
Separate minimum Inspector connect from ordered binding replay, and publish
unobserved initialization facts without snapshots or completion fences.
Retire Browser contributions immediately and supervise cleanup using the
original native authority, including failed or replaced connections.
The fixture renderer is not modal-blocked (the pushed dialog only
publishes connection-level state), so the deferred apply settles as
soon as its dispatch runs instead of staying parked behind a live
modal: the completion arrives as success and finishes cleanly. Assert
that, and cover the scheduler warn-path contract by injecting a
failure directly into the completion. Renderer death while the apply
is parked behind a production modal stays covered by the websocket
integration test.
Chromium resolves Target.attachToTarget in ~0 ms even when the target
shows a modal alert/confirm/prompt; moli parked the attach response
behind the renderer's modal wait because the attachment binding apply
was awaited before the commit.
Defer the binding apply instead: a dialog that is already published for
the target (or one that opens while the apply waits) hands the
still-queued dispatch to a supervised background wait, and the attach
commits immediately. The apply settles once the renderer frees up and
its completion is consumed by the scheduler with the same failure
tolerance as the synchronous path, minus the response predecessor
fence that no longer orders anything after publication. Renderer FIFO
still keeps the new session's first command behind the bindings.
createTarget/setAutoAttach share the broader dispatch path and remain
follow-up work.
Place the large navigation state machine on the heap before retained command workflows poll it. This bounds the production navigation stack while preserving the original cancellation, reply-boundary and retained-result behavior under the default Rust thread stack.
Retain the native Worker loading pipeline from main and apply the instance policy and execution origin to streamed and buffered Fetch/XHR responses. Observe Network completion on the actual Worker session in policy regression tests.
Resolve the selected root once and recheck path components before queued traversal, backing creation and lazy reads. Preserve the chosen root name and explicit file selection behavior. These are best-effort pathname checks; check/open races and file identity replacement remain outside this change.
Give each load a stable native network handle and single-use interception ports. Keep Worker Promise settlement separate from network completion, route observations to Worker targets, and remove the parent request table and continuation messages.
Cover cancellation, streaming, request overrides, authentication, CSP and Service Worker responses. Keep the bucket-deletion test transaction active until retirement instead of racing its normal auto-commit.
Retain immutable Blob backing after authorizing the initiating Document storage key and partition. Stream bounded chunks through the existing download artifact lifecycle and report unavailable local Blob URLs as canceled downloads.
Include the Playwright callback regression from #2970, large Blob transport and artifact checks, permission isolation, read-error cleanup and cancellation coverage.
Consolidates #2970.
Fixes#2932.