Write-up published
Resolved
Version 2.36.60 of the Push extension became available at 1:18am UTC on the Chrome store, which contains the fix for this issue. A full writeup of the root cause will follow.
Identified
After further investigation, we have confirmed that the impact is not limited to App banners. When the Push extension goes into a degraded state where it has lost communication with tabs using Edge energy saver mode, the following Push capabilities could also work intermittently or be delayed in firing.
Controls:
Phishing tool detection
Cloned login page detection
Password protection
Stolen credential detection
Strong password enforcement
MFA enforcement
Password logging prevention
Malicious copy and paste detection
App banners
File upload blocking
Clipboard blocking
Custom detections
Telemetry:
Password login detection
FedCM login detection
MFA data collection
File uploads
This issue was first introduced in v2.36.17 of the Push extension and has been fixed in the upcoming release v2.36.60.
Note: This issue only impacts Edge browsers. Other browsers are not affected.
Self-remediation option:
We recommend you disable energy saving features in Edge to avoid tabs being put to sleep. This will serve as a workaround until the new version of the extension is available.
Identified
We are investigating an issue affecting the App banners feature that results in banners failing to appear consistently in Edge.
This issue occurs when Edge applies energy saving settings to tabs that haven’t been used recently, putting them to sleep. When this happens, the Push extension cannot consistently communicate with any Edge browser tabs, causing delayed or intermittent firing of controls.
We are working to identify whether any other controls besides App banners are also impacted by this issue, and will update this page with more information.
We have already identified a solution to this issue and sent v2.36.60 of the Push extension to the extension stores for release, pending the normal review process.