MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: Find Filter button broken when going through StartAsync API

Open
#5,414 2 comments 1 reaction 1 assignee View on GitHub

@Navdeep-ss is already working on this.

Since Nov 20, 2025.

bug
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

When intercepting Ctrl+F and showing the Find popup with StartAsync, the Filter button doesn't do anything.

This works fine when not using the StartAsync API.

Importance

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

Runtime Channel

Prerelease (Edge Canary/Dev/Beta)

Runtime Version

143.0.3648.0 canary

SDK Version

3530.0

Framework

Winforms

Operating System

Windows 11

OS Version

26100.6899

Repro steps

Download WinForms sample app

In WebView2Control_CoreWebView2InitializationCompleted, add: this.webView2Control.CoreWebView2.Settings.AreBrowserAcceleratorKeysEnabled = false;

Update the existing WebView2Control_KeyDown to:

    private void WebView2Control_KeyDown(object sender, KeyEventArgs e)
    {
            var find = this.webView2Control.CoreWebView2.Find;
            if (e.KeyCode == Keys.F)
            {
                var options = webView2Control.CoreWebView2.Environment.CreateFindOptions();
                options.FindTerm = "";
                find.StartAsync(options);
            }
   }
  1. start app using Canary Edge
  2. press Ctrl+F
  3. Clicking Filter button does nothing.
  4. If the Filter button were previously toggled on, it will show it but then toggling it off causes issues

Image

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

No, this never worked

Last working version (if regression)

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.