[Problem/Bug]: F3 with Find popup doesn't behave correctly when not focused on the Find popup

[pushkin-]

What happened?

when focused on the window while the Find popup is up, pressing (shift)+F3 jumps my search results to a non-sequential result.
So I might be on result 8, focus on main window and press F3 and I get jumped to result 2.

Haven't found a pattern for this.

discovered this repros in Edge browser, so maybe this issue needs to go somewhere else.

Importance

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

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

126.0.2592.61

SDK Version

1.0.2535.41

Framework

Winforms

Operating System

Windows 11

OS Version

10.0.22631 Build 22631

Repro steps

1. use the WinForm sample here: https://github.com/MicrosoftEdge/WebView2Samples/tree/main
2. run and press Ctrl+F
3. search for sdk
4. see 90 or so results
5. if you're focused in the popup and press F3, it advances correctly (1, 2, 3, 4, / 91)
6. If I advance to 10 (as an example), and then focus on the main window and press F3, the Find popup search resets to 2/91.

Repros in Edge Browser

Yes, issue can be reproduced in the corresponding Edge version

Regression

No, this never worked

Last working version (if regression)

No response

[pushkin-]

a similar thing seems to repro in Chrome.
This behavior seems to be hinted at in the docs:

calling Start again during an ongoing find session does not resume from the point of the current active match. For example, given the text "1 1 A 1 1" and initiating a find session for "A", then starting another find session for "1", it will start searching from the beginning of the document, regardless of the previous active match.

[shrinaths]

Try one of the current runtime versions > 1.0.3415. Search continues from the current position. The current position may change, should the user decide to scroll up or down through the page. This is not the same as saying the previous find highlighted position. A number of actions may invalidate the previous position including changing the search term. Closing this as by design.

[pushkin-]

What do you mean by version 1.0.3415. What is "1.0" - I though that was just for SDK versions. Or do you mean any stable version where the third piece is at least 3415? The latest I see is 3405 here: https://learn.microsoft.com/en-us/deployedge/microsoft-edge-relnote-beta-channel

[ajtruckle]

The whole thing is confusion. My feedback seems ignored which is a shame. Can’t speak for anyone else.

[pushkin-]

ah ok, you're talking about the SDK version, not runtime. I tried with that version and see the same behavior.
I'm not scrolling up or down.
I just click in the webpage and press f3 again, and then found result jumps from 10/117 to 2/117 for some reason.

Just to double check, you're saying that this is expected behavior?

I can repro this with Edge, so alright.. but still seems odd to me