Deprecation of JavaScript "unload" event

[gp73025452]

we have received the following notice from one of our partners:

I am reaching out regarding the upcoming deprecation of the JavaScript unload event in Chromium-based browsers, including Google Chrome and Microsoft Edge. This change is expected to be fully enforced by Q2 2025 and may impact the functionality of SCORM content hosted on our platform. As part of this deprecation, content that relies on the unload event for bookmarking, course completion, or other interactions may no longer function as expected. To prevent any disruption, we kindly request that you review and update your content to replace the unload event with the recommended pagehide event or other suitable alternatives.

Please advise if this will affect our existing and updated Adobe Captivate classic and Adobe Captivate 12.4 version SCORM packages? 

[RodWard]

You have addressed this question to the Adobe Captivate User Forum.  This is NOT Adobe Help or Adobe Technical Support.

We're just a bunch of Captivate users like yourself.

Other users have been asking this same question, but so far I have not seen any definitive answer from Adobe.

[craigb870039]

Here in 2025 and being asked to troubleshoot Captivate-developed courseware, so while Adobe Technical Support appears to be unresponsive, maybe the brightest Captivate developers out there have come up with a post-packaged hack to preempt the unload() event. Has anyone confirmed via SCORM Cloud log files that a commit call is made just prior to unload (assuming a 'normal' exit occurs, not "x'ing" out)?