Start iframe-input with --scrollbars so its nested native control checks
continue to exercise visible scrollbars. Add a default scrollbar-visibility
group covering fetch/serve defaults, boolean environment values and CLI
precedence, geometry, stable gutters, frames, PNG output and input routing.
Cover CDP toggling, navigation, target isolation, detach, resize and layout
dependencies in independent processes with explicit environments.
Validation: 43 harness unit tests passed; scrollbar-visibility (22 scenarios),
iframe-input and classic-scrollbar smoke groups all passed (3/3).
Apply scrollbar hiding to the live Page before acknowledging the command, preserve the startup flag, and replay the target setting before navigation scripts. Validate the required boolean and layout mode, track per-session state, and clear overrides on detach.
Refs #1081
Hide native scrollbars and automatic gutters while preserving scrolling and explicit stable gutters. Require layout mode and retain the setting across navigation, frames, and protocol sessions.
Refs #1081
Exercise Range requests through buffered, HTML and raw transports, including malformed or empty Range values, native header configuration and redirects. Inspect wire headers to ensure identity encoding is selected for Range without leaking into subsequent ordinary requests, while response decompression remains active.
Run the 451451cec release against WPT db95fafd1f with the full all profile,
CDP mode, and 50 workers. Record all 13,631 executed cases: 9,583 passed,
3,724 failed, 259 timed out, 10 errored, 1 crashed, and 54 stalled.
Both Promise and both Wasm entry-settings regressions now pass in the full
run and in all five focused release rounds. Keep the other original full-run
statuses, including errors and intermittent failures; diagnostic comparisons
with main and the previous release do not replace snapshot results.
Audit confirms every raw result agrees with the engine report, matrix, and
eight sorted, disjoint status lists, with no missing or unexecuted cases.
A popup-scoped identity lookup can miss a load callback created in its
parent or another live iframe. The retirement guard then rejects the
callback solely because its context has a Window token, causing the
Promise and Wasm entry-settings WPTs to time out.
Resolve the callback creation context's concrete registration when no
scoped identity was provided, then apply the existing currentness check.
Unregistered Window realms remain retired and captured identities retain
their original authority.
Add a Page-task regression that opens a popup through an iframe and checks
parent and live-child callbacks, their receivers and event targets. A
callback retained from a removed/reinserted iframe Window must not run.
Validation: cargo fmt --all; workspace/all-targets/all-features Clippy with
-D warnings; cargo nextest run --no-fail-fast with retries disabled
(19,166 passed, 16 skipped). The new regression passes 20 stress iterations;
the 60 popup and callback-retirement tests pass all three stress rounds.
Run the unfiltered all profile with release Moli 1.1.12 built from
0c5f83969f after rebasing onto main
8f7598a30f, using WPT
db95fafd1fcef8428805e41eb5705d444e8c67ce and 50 CDP workers.
Complete all 13,631 cases: 9,578 pass, 3,730 fail, 261 timeout, 9 error,
one crash and 52 harness-stalled. Against main's lists, 11 cases gain pass
and 16 lose pass, for a net decrease of five. Preserve the raw full-run
outcomes.
Validate the unchanged case set and exactly one recorded result per case.
Raw live results, engine output, matrix and all eight sorted, disjoint,
exhaustive status lists agree. No setup errors, missing cases, unknown
statuses or unexecuted recovery placeholders. git diff --check passes.
Check all 16 pass losses against the same release main source and WPT.
Four Promise/Wasm entry tests reproduce a source regression: HEAD times
out in 8/8 paired trials while main passes 8/8. The callback retirement
guard added in 77d2700c6 is the cause; a diagnostic-only fallback restores
all four in 3/3 trials. Keep these failures in the raw timeout list.
Nine losses also fail on main; two original failures remain unreproduced.
rel-attribute-clearing remains suspicious (HEAD 3/28 failures, main 0/28).
Filtered validation does not alter this full-run snapshot.
Keep the private Document wrapper slot and Window.document getter together in
the Window binding layer. Bind environment settings and the wrapper through
one guarded entry point, leaving WindowEnvironmentSettings responsible for
native document identity, origin and base URL resolution.
Validation: cargo fmt --all; cargo clippy --workspace --all-targets --all-features
-- -D warnings; cargo nextest run --no-fail-fast.
Resolve Window.document through the receiver realm's retained settings and
keep its original Document wrapper in a private V8 slot after cache retirement.
Use the same getter for the LegacyUnforgeable bootstrap descriptor.
Cover cleanup, reinsertion, borrowed getters and navigation, including retained
Request regressions for about:blank, srcdoc and HTTP frames.
Validation: cargo fmt --all; cargo clippy --workspace --all-targets --all-features
-- -D warnings; cargo nextest run --no-fail-fast (19,146 passed, 16 skipped).
Keep each child realm's associated native Document and captured origin after
execution authority retires. Saved Request constructors continue reading live
base changes on that Document and cannot resolve against a reinserted iframe.
Keep removed Window globals attached, detach only for same-frame proxy reuse,
and explicitly reject retired Window callback realms. Preserve initial empty
Document bootstrap resolution and use intrinsic abort constructors internally.
Cover about:blank, srcdoc, HTTP, realm cleanup, base mutation, reinsertion,
referrers and dependent signals. Existing MessagePort retirement and nested
blob iframe constructor tests remain unchanged and pass.
Validation: cargo fmt --all; workspace Clippy with all targets/features and
-D warnings; full nextest (19,144 passed, 16 configured skips, no retries).
A one-millisecond timer could become runnable immediately after registration.
Remove the early dispatch allowance from the shared scheduler so registered
and rescheduled timers become runnable only at or after their actual
monotonic deadline. All readiness queries use the same rule.
Regression coverage checks registration-time and pre-deadline queries,
exact-deadline dispatch through filtered and unfiltered paths, and interval
rescheduling without advancing the new deadline.
Capture each IdleDeadline's native performance time origin and subtract
coarsened timestamps in ticks. This keeps timeRemaining on the same 100us
timeline as performance.now, including when the method is borrowed from
another realm, and avoids exposing floating-point sub-tick residuals.
The recursive idle WPT regression is reproducible at 8a353fa2a: its release
parent passes 20/20 while that commit fails 20/20. That commit changed the
DOM clock from 5us to 100us without updating the raw idle deadline clock.
Add deterministic clock-bucket and expiration checks plus a native API
resolution test that fails before this fix. Clock-only release stress passes
97/100; the remaining failures expose early idle timer admission, which is
handled separately.
Validation: cargo fmt --all; cargo clippy --workspace --all-targets
--all-features -- -D warnings; cargo nextest run --no-fail-fast
(19139 passed, 16 skipped).
ldm0