FredApps ee081d033e fix(scripts): keep timers past a refused script; page actions before timers ...

A script refused before it runs (too long, or nested too deeply) left the
realm untouched but reported no timers. The viewer keeps only the timers
a run reports, so a button or console script over the limit stopped every
page timer. The realm now reports the timers it still has on that path.

The viewer built the page actions' run and the timers' run before it
handled either, so a due timer ran before what the page's open action
asked for: on a page that goes on to another, before that page's close
action could stop it. The timers now run after the page actions, and only
if those left the page, the tab and the dialogs as they were; otherwise
they wait a frame. The focused field's editor text is taken before each
run, not once for both.

Tests: a_script_refused_before_it_runs_reports_the_realms_timers (js),
a_script_refused_before_it_runs_keeps_the_pages_timers (engine),
timers_wait_for_the_page_a_page_action_goes_to (ui). Each fails without
its fix.

2026-11-11 19:48:17 +01:00

..

fuzz

Fuzz target for the JavaScript engine's script runner (#6304)

2026-11-05 20:11:15 +01:00

src

fix(scripts): keep timers past a refused script; page actions before timers

2026-11-11 19:48:17 +01:00

Cargo.toml

…