You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting with WebView2 Runtime version 139,
the behavior of the Restart button
(located at the bottom-right of the edge://flags page)
when a flag is modified,
(and the edge://quit page behiavor) has changed significantly:
These actions now immediately terminate the application by sending a WM_CLOSE message.
If the WM_CLOSE message is ignored, a ProcessFailed/UNEXPECTED event is triggered.
Unfortunately, it's not possible to distinguish whether the WM_CLOSE was sent by WebView2, making it impractical to handle gracefully.
Prior to Version 139:
The Restart button and edge://quit page would only trigger a ProcessFailed/UNEXPECTED event, 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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
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