Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Problem/Bug]: AreBrowserAcceleratorKeysEnabled broken in Canary/Dev release channel #5033

Open
pushkin- opened this issue Jan 6, 2025 · 1 comment
Assignees
Labels
bug Something isn't working regression Something used to work but doesn't anymore tracked We are tracking this work internally.

Comments

@pushkin-
Copy link

pushkin- commented Jan 6, 2025

What happened?

With dev and canary webview2 runtime (133.0.3014.0 dev), AreBrowserAcceleratorKeysEnabled is no longer respected.

So I set that property to false, but Ctrl+R, F12, etc still work.

Doesn't repro with beta channel or stable (Edge 132)

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Prerelease (Edge Canary/Dev/Beta)

Runtime Version

133.0.3014.0 dev

SDK Version

1.0.2535.41

Framework

Winforms

Operating System

Windows 11

OS Version

22631.4602

Repro steps

In minimal WinForms sample, in WebView2Control_CoreWebView2InitializationCompleted, add webView2Control.CoreWebView2.Settings.AreBrowserAcceleratorKeysEnabled = false;

start app and see that Ctrl+F/F12/Ctrl+R all work

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Regression in newer Runtime

Last working version (if regression)

runtime 132.0.2957.93 beta

AB#55711753

@pushkin- pushkin- added the bug Something isn't working label Jan 6, 2025
@github-actions github-actions bot added the regression Something used to work but doesn't anymore label Jan 6, 2025
@ambikakunnath ambikakunnath added the tracked We are tracking this work internally. label Jan 7, 2025
@ambikakunnath
Copy link
Member

Thanks for reporting the issue. Created an internal bug to track and fix the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working regression Something used to work but doesn't anymore tracked We are tracking this work internally.
Projects
None yet
Development

No branches or pull requests

2 participants