Forum Discussion
Power BI Embedded registers blocked unload handler in Microsoft Edge
We embed Power BI reports in an ASP.NET Core Blazor Server application. Microsoft Edge 152 logs this warning whenever an embedded report is loaded:
[Violation] Permissions policy violation: unload is not allowed in this document.
The report itself renders correctly. The warning originates in the Power BI hosted reportembed script, not in our application code. We tested the available Permissions-Policy header and iframe allow configurations. The embedded Power BI frame remains unable to use unload in every case.
Is this expected during the Chromium unload deprecation rollout? If so, is there a planned change to replace the unload listener with a supported page lifecycle event?
Environment: Microsoft Edge 152.0.4191.66, ASP.NET Core Blazor Server, Microsoft.PowerBI.JavaScript.
1 Reply
- LumericVisuals
Helper I
This is almost certainly Chromium's ongoing unload event deprecation surfacing in a script you don't control, rather than anything wrong in your embedding code. The warning names the Power BI hosted reportembed script specifically, and Edge/Chrome have been tightening enforcement around unload listeners for a while now as part of the back/forward-cache work — sites still get flagged even when the listener is legitimate.
In practice this is usually just console noise rather than a functional break — the report itself still renders and works, per what you're already seeing. Worth double-checking that nothing real regressed (state not saving on close, telemetry gaps) before spending more time on it, since a console warning alone doesn't tell you whether anything actually stopped working.
Since the listener lives in Microsoft's own script rather than your application code, there's no fix you can apply from the embedding side — you'd only be able to suppress the console noise, not the underlying registration. If it's bothering you beyond cosmetics, the powerbi-client-sdk-typings / JavaScript SDK GitHub repo is the right place to check for an existing issue or file a new one; I don't have visibility into whether Microsoft has already shipped a pagehide/visibilitychange replacement in a recent SDK version, so that's worth confirming directly rather than taking on faith.