[Problem/Bug]: Webview2 returning different format in response after version update #5349
Description
What happened?
When users receive update to latest WebView2 the response format changes, causing one of our login controls to break on older releases
Users can pin to previous versions of WebView2 to fix this, but not all users are able to do this easily (thousands of machines in some orgs)
When calling
string html = await Browser.ExecuteScriptAsync("document.documentElement.outerHTML;");
we get a different result depending on webview2 version
name=\"wresult\" value=\"\u003Cwst:
vs
name=\"wresult\" value=\"<wst:
The internal value is being changed from unicode to urlencoding for symbols like <
This change in format is breaking previously released login controls
Importance
Blocking. My app's basic functions are not working due to this issue.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
139.0.3405.86 or newer
SDK Version
No response
Framework
WPF
Operating System
Windows 11, Windows 10
OS Version
No response
Repro steps
Method ExecuteScriptAsync and view response format not Unicode formatted after new version
Repros in Edge Browser
Yes, issue can be reproduced in the corresponding Edge version
Regression
Regression in newer Runtime
Last working version (if regression)
138.0.3351.121