From ba0f9f96d2dce2a97802c7ded4001194352eab27 Mon Sep 17 00:00:00 2001
From: Grantmartin2002 <69131375+Grantmartin2002@users.noreply.github.com>
Date: Wed, 26 Aug 2026 14:01:08 -0500
Subject: [PATCH] fix(v3/windows): raise the WebView2 embed timeout to 60s

A cold WebView2 launch on a loaded CI runner occasionally takes longer
than 30s, so Embed gave up and TestCookieManager failed. The timeout is
a backstop for a callback that never arrives, not a startup budget, and
it costs nothing when initialisation succeeds.
---
 v3/internal/webview2/pkg/edge/chromium.go | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/v3/internal/webview2/pkg/edge/chromium.go b/v3/internal/webview2/pkg/edge/chromium.go
index 947727fa1c0..f8895aa4692 100644
--- a/v3/internal/webview2/pkg/edge/chromium.go
+++ b/v3/internal/webview2/pkg/edge/chromium.go
@@ -234,7 +234,7 @@ func (e *Chromium) Embed(hwnd uintptr) bool {
 // embedTimeout bounds how long Embed waits for CreateCoreWebView2Controller to
 // complete. Controller creation is normally well under a second; this is a
 // backstop for the case where the callback never arrives, not a budget.
-const embedTimeout = 30 * time.Second
+const embedTimeout = 60 * time.Second
 
 // pumpUntilInited runs a message loop until the controller is ready, the queue
 // receives WM_QUIT, or timeout elapses. It reports whether the controller