Replies: 1 comment
-
|
This problem seem fixed from runtime version 142 : runtime versions 139, 140, 141 : |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Starting with WebView2 Runtime version 139,
the behavior of the Restart button
(located at the bottom-right of the
edge://flagspage)when a flag is modified,
(and the
edge://quitpage behiavor) has changed significantly:WM_CLOSEmessage.WM_CLOSEmessage is ignored, aProcessFailed/UNEXPECTEDevent is triggered.WM_CLOSEwas sent by WebView2, making it impractical to handle gracefully.Prior to Version 139:
edge://quitpage would only trigger aProcessFailed/UNEXPECTEDevent, allowing the application to respond appropriately.I believe this new behavior is problematic for most applications.
The previous approach used in WebView2APISample was more user-friendly: it prompted the application to recreate the WebView window rather than abruptly terminating it.
Now, the application is closed without warning or explanation, which can lead to a poor user experience.
Beta Was this translation helpful? Give feedback.
All reactions