[Problem/Bug]: Find filter don't persist when using Find APIs

[pushkin-]

What happened?

This works fine when enabling accelerator keys and allowing the native Find behavior.

But when I disable AreBrowserAcceleratorKeysEnabled and intercept Ctrl+F and call StartAsyncmyself, after setting some filters, closing and reopening the Find popup twice, the filter selection is cleared.

Importance

Moderate. My app's user experience is affected, but still usable.

Runtime Channel

Stable release (WebView2 Runtime), Prerelease (Edge Canary/Dev/Beta)

Runtime Version

143.0.3603 canary

SDK Version

3530.0

Framework

Winforms

Operating System

Windows 11

OS Version

26100.6584

Repro steps

Download minimal WinForms sample. In BrowserForm.cs::WebView2Control_CoreWebView2InitializationCompleted, add in: this.webView2Control.CoreWebView2.Settings.AreBrowserAcceleratorKeysEnabled = false;

Replace WebView2Control_KeyDown with:

    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. press Ctrl+F
2. search something
3. change the filter (e.g. match case)
4. close and reopen the Find popup
5. notice filter is still set
6. close and reopen the Find popup
7. notice the filter selections are cleared

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

[pushkin-]

though I see we can configure what filters are used when calling StartAsync. So I wonder:

1. Why does it work fine the first time and then resets
2. How can we tell the API to use the previous terms? Maybe if a value isn't set for ShouldMatchWord, for instance, it should use the filter value selected by the user.

[pushkin-]

Also, I can make another issue if desired, but if I set options.ShouldMatchWord=true; and call StartAsync, the first time I call it, the filter option isn't respected. It's respected for subsequent calls though.

[Navdeep-ss]

There was an issue, we have identified it and will fix it soon.
Ideally, during a programmatic find, the options set in findOptions should be respected. Currently, this is happening correctly; however, the Find bar UI is not properly synchronized with those values. As a result, the Find bar may display incorrect options, even though the underlying find operation is working as expected.