Problem:
With the release of Chrome (146.0.7680.72) and later, MET/TEAM is returning an error.
After this update, you can no longer close screens in MET/TEAM after clicking on Save icon. The Save works correctly, but when you click the "Close" button, such as on the Work Order screen, we get the message:
/msdyn_blobfile/$value)
However, there’s nothing to save—the SAVE button is greyed out.
Selecting Yes or No just returns you to the Work Order screen, so you end up stuck in a loop.
Issue:
This error is a result of Google Chrome's final phase of the unload event deprecation, which reached 100% of users in early 2026. Chrome (and other Chromium-based browsers) now blocks these listeners by default to support the Back-Forward Cache (bfcache) and improve performance.
1. The Error Message
When a site attempts to use the unload event in Chrome 146+, the browser will block it and log a violation in the DevTools Console. You can use this snippet as an example of what users see:
[Violation] Permissions policy violation: unload is not allowed in this document. (Check the Console tab in DevTools to find this error.)
Temporary Resolution:
Turn off a flag Chrome
Type in Chrome address bar the following:
chrome://flags/#deprecate-unload
Then you will find “Deprecate the unload event” flag and you need to Disable it.
/msdyn_blobfile/$value)
Long Term Resolution:
Fluke’s Software Engineering team is aware of this issue and are actively pursuing a permanent solution to this issue by updating the MET/TEAM code base, which will be released in a future version
With the release of Chrome (146.0.7680.72) and later, MET/TEAM is returning an error.
After this update, you can no longer close screens in MET/TEAM after clicking on Save icon. The Save works correctly, but when you click the "Close" button, such as on the Work Order screen, we get the message:
However, there’s nothing to save—the SAVE button is greyed out.
Selecting Yes or No just returns you to the Work Order screen, so you end up stuck in a loop.
Issue:
This error is a result of Google Chrome's final phase of the unload event deprecation, which reached 100% of users in early 2026. Chrome (and other Chromium-based browsers) now blocks these listeners by default to support the Back-Forward Cache (bfcache) and improve performance.
1. The Error Message
When a site attempts to use the unload event in Chrome 146+, the browser will block it and log a violation in the DevTools Console. You can use this snippet as an example of what users see:
[Violation] Permissions policy violation: unload is not allowed in this document. (Check the Console tab in DevTools to find this error.)
Temporary Resolution:
Turn off a flag Chrome
Type in Chrome address bar the following:
chrome://flags/#deprecate-unload
Then you will find “Deprecate the unload event” flag and you need to Disable it.
Long Term Resolution:
Fluke’s Software Engineering team is aware of this issue and are actively pursuing a permanent solution to this issue by updating the MET/TEAM code base, which will be released in a future version