On 19 June 2026 at 10:54am UTC, Push Security received a report from a customer that App banners were not working consistently for users on Microsoft Edge. After investigating, the Push team found that the issue was caused by the Push extension being unable to communicate with Edge browser tabs that were inactive — Microsoft Edge applies energy-saving features that put inactive tabs to sleep. In cases where the Push extension encountered inactive Edge browser tabs, several Push controls could not fire consistently, or were delayed in firing.

The issue was resolved for all customers on Friday, 26 June 2026 with the release of v2.36.60 of the Push extension.

• 19 June 2026 10:54am UTC: Initial report from customer saying that App banners were not working consistently on Microsoft Edge browsers. The team started investigating.

• 23 June 2026 6:53pm UTC: Issue discovered and started working on fix.

• 24 June 2026 7:10pm UTC: Testing of fix completed and new extension release issued to extension stores.

• 26 June 2026 1:18am UTC: v2.36.60 of the Push extension became available on the Chrome store.

Version 2.36.17 of the Push extension, released on 8 June 2026, included an update to support a new control. This update introduced a slightly different communication mechanism used between the Push extension and open tabs than other controls. In the past on other controls, the extension would communicate with open tabs to deliver settings without waiting for a response from the tab. For the new control, the extension waited for tab responses before allowing the extension to continue with normal execution. For Edge tabs in an energy-saving state (e.g. edge://settings/system/managePerformance), this meant that the extension never got a response and was subsequently stuck in a waiting state. When in this state, the Push extension would have a delayed (or no response) to an active tab waiting for a control decision. This meant that Push could not receive certain telemetry events or apply some controls on Edge where these frozen tabs were present.

The following Push capabilities were impacted on Edge browsers:

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

Our testing confirmed that no other browsers were impacted because they handle energy-saving settings differently from Edge.

In analyzing the impact to customers, the team noted a slight decrease in App banner events for the impacted timeframe for a small number of customers. Unfortunately, due to the wide variety of user and tab behavior for this timeframe, and the nature of the issue, Push is not able to further quantify the impact or to provide missed events for the affected period.

V2.36.60 contains a fix for this issue that does not wait for a response from frozen (sleeping) tabs. The Push team has developed a battery of new test suites for sleeping tabs and other energy-saving features on Edge.