From 2ee398b6d5aee667635e97f9f49ec1f59e4e80fe Mon Sep 17 00:00:00 2001
From: Karl Seguin <k@openmymind.io>
Date: Mon, 4 May 2026 11:31:02 +0800
Subject: [PATCH] On window.close, reset the frame's scheduler

Saw that worker.close() does this and it makes sense to do for window.close()
too.
---
 src/browser/webapi/Window.zig | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/browser/webapi/Window.zig b/src/browser/webapi/Window.zig
index 29243e7c..03698f9c 100644
--- a/src/browser/webapi/Window.zig
+++ b/src/browser/webapi/Window.zig
@@ -568,6 +568,8 @@ pub fn close(self: *Window) void {
         }
     }
 
+    frame.js.scheduler.reset();
+
     // We can't tear the Frame down here — close() is invoked from JS still
     // running on top of this Frame's V8 context, often deep inside a script
     // eval whose parser is still holding the Frame. Destroying the context