[Problem/Bug]:

What happened?

With Webview2 runtime 133, the following issue was introduced:

Press CTRL+F to open default search dialog of Webview2. Search for some text which actually exits on the page. The results will be highlighted. Now turn visibility of Webview2 off. The default search dialog becomes hidden, too. So far, so good. Now turn visibility of Webview2 on again. The search results on the page are still highlighted, so the search session is still active, but the search dialog is not displayed. Trying to open it by CTRL+F fails. After reloading the page or navigating away from it, a new search can be started by CTRL+F and the default search dialog is displayed again.

With webview2 runtime 132 the issue didn't occur.

Importance

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

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

133.0.3065.82

SDK Version

1.0.2903.40

Framework

Win32

Operating System

Windows 11

OS Version

No response

Repro steps

Press CTRL+F to open default search dialog of Webview2. Search for some text which actually exits on the page. The results will be highlighted. Now turn visibility of Webview2 off. The default search dialog becomes hidden, too. So far, so good. Now turn visibility of Webview2 on again. The search results on the page are still highlighted, so the search session is still active, but the search dialog is not displayed. Trying to open it by CTRL+F fails. After reloading the page or navigating away from it, a new search can be started by CTRL+F and the default search dialog is displayed again.

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Regression in newer Runtime

Last working version (if regression)

SDK 1.0.2903.40, Runtime 132.x