[Problem/Bug]: FindNext/FindPrevious doesn't seem to do anything

[pushkin-]

What happened?

I start a Find session:

CoreWebView2FindOptions findOptions = focusedWindow.ActiveWebView.CoreWebView2.Environment.CreateFindOptions();
focusedWindow.ActiveWebView.CoreWebView2.Find.StartAsync(findOptions);

When focused in the Find popup, I can press F3 to go to the next search.

When I focus in the main window and press F3 (which will be intercepted by our code, and we'll call):

CoreWebView2FindWrapper findInterface = focusedWindow.ActiveWebView.CoreWebView2.Find;
findInterface.FindNext();

nothing happens.

It seems like we might have to be focused on the Find popup for that to work, but I don't see any Focus() API for the Find interface. It would be nice if that automatically moved focus to the Find UI and navigated to the next search result.

Before calling FindNext, I can inspect the Find interface and see that it's active and it has found some searches:

This works fine in browsers.

Importance

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

Runtime Channel

Prerelease (Edge Canary/Dev/Beta)

Runtime Version

134.0.3101.0 canary

SDK Version

1.0.3079.0 prerelease

Framework

Winforms

Operating System

Windows 11

OS Version

23H2 - 22631.4602

Repro steps

can post an example if you'd like

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-]

any updates? I'm considering implementing my own Find popup to work around other bugs, but can't do that since these APIs don't work.

[Navdeep-ss]

@pushkin- I did the same thing in winforms sample app and form me whenever I call find next, the next item gets highlighted. As you mentioned in your case nothing is happening, is it possible for you to share a small winform sample app which showcase that findNext doesn't work.

as you can also see in the gif, clicking on find next, highlighting the next matching word

[pushkin-]

I downloaded the WinForms sample app and made these adjustments:

In BrowserForm.cs, in WebView2Control_CoreWebView2InitializationCompleted, added:

 this.webView2Control.CoreWebView2.Settings.AreBrowserAcceleratorKeysEnabled = false;

Replaced WebView2Control_KeyDown's body with:

var find = this.webView2Control.CoreWebView2.Find;
 if (e.KeyCode == Keys.F)
 {
     var options = webView2Control.CoreWebView2.Environment.CreateFindOptions();
     options.FindTerm = "";
     find.StartAsync(options);
 }
 else if (e.KeyCode == Keys.F3)
 {
     find.FindNext();
 }

Then I start the app, press Ctrl+F, search for something, and then press F3 which triggers the FindNext API. Nothing happens in the app.

Oh I just realized that if I set FindTerm to a non-empty string, then it starts working... In my case, I don't have any initial term I want so I set it to empty string to clear out the previous term.

[Navdeep-ss]

So, I think there was some confusion regarding the use of FindNext/FindPrevious, and since I also validated that these two api works properly when you have a search term, closing this bug.

[pushkin-]

@Navdeep-ss Ok but they don't work when you pass in an empty string which is what I'm doing. Can you investigate that?

[Navdeep-ss]

Empty string is not suppose to work.

[pushkin-]

Actually, I misspoke. In my actual app, I'm passing a space character, and I have problems.
Specifically, if I search for a different term, f3 will search for the initial term that was passed into FindTerm rather than the new term.