Uncaught ReferenceError: ClipboardItem is not defined

Just got off the phone with Microsoft support. They have an internal product bug logged already and are working on a fix that is estimated to be deployed either this Friday or next. The main workaround as many have already mentioned is switching to https or using the chrome hack that was also mentioned in this thread.

Uncaught ReferenceError: ClipboardItem is not defined - Power BI Embed in WebView Suddenly Failing

Hi Power BI Community,

We've been using Power BI embedded reports inside a production application via WebView for quite a while now - everything was stable. However, very recently, we've started encountering the following error in the browser console:

Uncaught ReferenceError: ClipboardItem is not defined

This error is triggered at the point of embedding the report using:

report = powerbi.embed(embedContainer, config);

Key Notes:

• Our application setup hasn’t changed - same config, same environment, and same WebView.
• This error only started appearing recently, possibly due to a change in the Power BI SDK (reportEmbed.min.js) or related service.
• Appears to be related to the Clipboard API - specifically ClipboardItem, which is not supported in some WebView contexts or over HTTP.

Community Echoes:

I noticed other developers are facing the exact issue across different platforms and embedding methods:

1. Long-running web apps suddenly breaking due to this error, without any recent code changes.
2. WPF applications using WebView2 now require serving the HTML file over HTTPS to work.
3. Issue seems tied to updates in Power BI's embed SDK - possibly stricter Clipboard API enforcement.
4. Some reports confirm that switching to HTTPS resolved the issue, even when HTTP worked fine before.

What I'm looking for:

• Has there been an official change or announcement from Microsoft regarding Clipboard API enforcement in the embed SDK?
• Any workaround to suppress or bypass ClipboardItem usage if clipboard functionality isn't needed?
• Can the Power BI product team confirm if reportEmbed.min.js was recently updated with breaking changes?

This issue is currently affecting our internal dashboards across environments. Any clarity or guidance would be greatly appreciated.

Thanks in advance!
- Puneeth

It's a bug in the powerbi script. It should check if ClipboardItem is available because it isn't always there. Microsoft forgot to put it inside a try/catch clause. ClipboardItem is not defined when:
- http:// is used in chromium without localhost
- cross-origin iframes (when you load powerbi using the javascript client api)

Another solution for MS is to put this code at the start of the injected iframe to mock the clipboard:

if (typeof ClipboardItem == 'undefined') {
    ClipboardItem = window.ClipboardItem = function (items) {
        return items;
    };
}

This is not possible to do yourself when you are embedding Powerbi inside your own website. That is because the cross-origin settings do not allow injecting javascript in the iframe. So I'm not able to produce a workaround for that situation.

It's only possible when using playwright:

await context.addInitScript(`
    if (typeof ClipboardItem == 'undefined') {
        ClipboardItem = window.ClipboardItem = function (items) {
            return items;
        };
    }
`);

Hi HasnainNutkani ,

Thank you for reaching out to the Microsoft Fabric Community.

The error message Uncaught ReferenceError: ClipboardItem is not defined is not caused by the Power BI JavaScript embedding functionality itself. Rather, it originates from usage of the Clipboard API specifically the ClipboardItem interface which is a browser-provided feature not supported in all environments.

This API is not part of the Power BI SDK, so the error is likely coming from custom application code or a third-party script that is being executed alongside or during the embedding process. As your integration has been stable for years, it’s possible that a recent change such as a browser update, added dependency, or modification in your app introduced this usage. It's also important to ensure the application is running in a secure (HTTPS) context and in a browser that supports the Clipboard API.

If the Power BI reports are rendering correctly and the error is only appearing in the console, it may be a non-blocking issue. However, if the embedding is being affected, we recommend reviewing any recent changes made to your app or libraries and checking the browser’s developer tools to locate the specific source of the error.

I hope this will resolve your issue, if you need any further assistance, feel free to reach out.

If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

Thankyou.

 Okay, so, as was mentioned in another post by v-tsaipranay, the ClipboardItem does need to be over HTTPS on a compatible browser. But from what I have found, it is indeed in the reportEmbed.min.js that comes through the Power BI SDK. 

I have found that changing all my links to HTTPS (was only ever internal) has fixed this. But I would still like to try and find out what exactly changed, as it was working over HTTP for well over a year without any issues up until yesterday morning. 

I was able to solve it momentarily with a configuration in Chrome:

chrome://flags/#unsafely-treat-insecure-origin-as-secure

Insecure origins treated as secure Treat given (insecure) origins as secure origins. Multiple origins can be supplied as a comma-separated list. Origins must have their protocol specified e.g. "http://example.com". For the definition of secure contexts, see https://w3c.github.io/webappsec-secure-contexts/ – Mac, Windows, Linux, ChromeOS, Android

I am getting the same issue myself now, which started occurring yesterday, as if Microsoft made an update to reportEmbed.min.js

 There have been zero changes to the embedded environment I created for months now, as it was working away without issue, so there is nothing on our end that would have introduced this error.

Now, we have no reports showing throughout our plant because of this. 
Screen just sticks on the following with the error in the console: 

Yep, we're seeing the same on embedded reports, since yesterday. No changes to config or environment

Yeah, this is unexpected. I have a WPF application with an embedded PBI report using WebView2 that suddenly stopped working, with the same error mentioned above. Had been working fine for months, loading a local HTML file as the webview source. If I spin up a simple webserver to serve the same HTML file over HTTPS, it works fine. Same code.

Something has changed, and it wasn't in our applications

I’m currently using an embedded service and encountering an error that says ClipboardItem is not defined. This issue appears in Chrome and Edge browsers, while it seems to work fine in Safari. Could you help me understand why this is happening?

Also, I’m using HTTP, and switching to HTTPS is not an option at the moment. Is there a way to resolve this issue so that the feature works correctly over HTTP as well?