From 012eeab3aa089aeef5d4862fbf97f94adbf995fb Mon Sep 17 00:00:00 2001
From: stffabi <stffabi@users.noreply.github.com>
Date: Thu, 7 Dec 2023 07:55:04 +0100
Subject: [PATCH] [windows] Fix #2359 by not redirecting the accelerators to
 wndproc

If someone wants to handle accelerators they could use the key
bindings in a cross-platform way.
---
 v3/pkg/application/webview_window_windows.go | 8 +-------
 1 file changed, 1 insertion(+), 7 deletions(-)

diff --git a/v3/pkg/application/webview_window_windows.go b/v3/pkg/application/webview_window_windows.go
index b53369141..32f71d25b 100644
--- a/v3/pkg/application/webview_window_windows.go
+++ b/v3/pkg/application/webview_window_windows.go
@@ -1322,13 +1322,7 @@ func (w *windowsWebviewWindow) setupChromium() {
 	chromium.WebResourceRequestedCallback = w.processRequest
 	chromium.ContainsFullScreenElementChangedCallback = w.fullscreenChanged
 	chromium.NavigationCompletedCallback = w.navigationCompleted
-	chromium.AcceleratorKeyCallback = func(vkey uint) bool {
-		if w.processKeyBinding(vkey) {
-			return true
-		}
-		w32.PostMessage(w.hwnd, w32.WM_KEYDOWN, uintptr(vkey), 0)
-		return false
-	}
+	chromium.AcceleratorKeyCallback = w.processKeyBinding
 
 	chromium.Embed(w.hwnd)