Reply to thread

Message

<blockquote data-quote="presntes" data-source="post: 1055985" data-attributes="member: 94929"><h2>Version 117.0.2045.12: August 29, 2023</h2>Fixed various bugs and performance issues.<h3>Announcement: Deprecating the unload event</h3>The Google Chrome team plans to deprecate the unload event starting in Chrome version 117. The deprecation will occur by gradually changing the default so unload handlers stop firing on pages unless a page explicitly opts in to re-enable them. For more information, see <a href="https://developer.chrome.com/blog/deprecating-unload/" target="_blank">Deprecating the unload event - Chrome Developers</a>, and <a href="https://groups.google.com/a/chromium.org/g/blink-dev/c/dvusqw9-IhI/m/SBkm_u1RAQAJ" target="_blank">Google Groups - Conversations</a>.While we haven&#039;t yet finalized the deprecation schedule, we anticipate that Microsoft Edge will follow Chrome&#039;s schedule with a possible delay of a release or two. If you&#039;re interested in testing with Microsoft Edge starting in version 118, the ForcePermissionPolicyUnloadDefaultEnabled policy will be available or you can use the instructions documented at <a href="https://github.com/fergald/docs/blob/master/explainers/permissions-policy-deprecate-unload.md#disable-unload-handlers-by-default-and-add-permissions-policy-to-opt-in-to-enabling-them" target="_blank">Disable unload handlers by default and add Permissions-Policy to opt-in to enabling them</a>.WebView2 will support both the permissions policy and the enterprise policy but won&#039;t be impacted by the gradual rollout in Microsoft Edge. We expect WebView2 will switch defaults when the roll out reaches 100% of page loads.<a href="https://learn.microsoft.com/en-us/deployedge/microsoft-edge-relnote-beta-channel" target="_blank">Release notes for Microsoft Edge Beta Channel</a></blockquote>

[QUOTE="presntes, post: 1055985, member: 94929"] [HEADING=1]Version 117.0.2045.12: August 29, 2023[/HEADING] Fixed various bugs and performance issues. [HEADING=2]Announcement: Deprecating the unload event[/HEADING] The Google Chrome team plans to deprecate the unload event starting in Chrome version 117. The deprecation will occur by gradually changing the default so unload handlers stop firing on pages unless a page explicitly opts in to re-enable them. For more information, see [URL='https://developer.chrome.com/blog/deprecating-unload/']Deprecating the unload event - Chrome Developers[/URL], and [URL='https://groups.google.com/a/chromium.org/g/blink-dev/c/dvusqw9-IhI/m/SBkm_u1RAQAJ']Google Groups - Conversations[/URL]. While we haven't yet finalized the deprecation schedule, we anticipate that Microsoft Edge will follow Chrome's schedule with a possible delay of a release or two. If you're interested in testing with Microsoft Edge starting in version 118, the [B]ForcePermissionPolicyUnloadDefaultEnabled[/B] policy will be available or you can use the instructions documented at [URL='https://github.com/fergald/docs/blob/master/explainers/permissions-policy-deprecate-unload.md#disable-unload-handlers-by-default-and-add-permissions-policy-to-opt-in-to-enabling-them']Disable unload handlers by default and add Permissions-Policy to opt-in to enabling them[/URL]. WebView2 will support both the permissions policy and the enterprise policy but won't be impacted by the gradual rollout in Microsoft Edge. We expect WebView2 will switch defaults when the roll out reaches 100% of page loads. [URL='https://learn.microsoft.com/en-us/deployedge/microsoft-edge-relnote-beta-channel']Release notes for Microsoft Edge Beta Channel[/URL] [/QUOTE]

Verification