Community Chat

Hello, I would like to ask for help or a workaround for an issue I am facing. I have created a JavaScript Fragment to be added to a web app/page. However, when I invoke the script, I receive the following message in the developer tools console window: "main.js:829 Refused to execute inline script because it violates the following Content Security Policy directive: 'script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules'". It seems that my code is being blocked from execution.

Interestingly, this problem does not exist in the web browser in my development environment. I am wondering if there is any workaround to bypass the Content Security Policy?

------------------------------
Terence Toledo
------------------------------

Hi Terence,

Please refer to the discussion post<o:p></o:p> and see if it can help you resolve the issue.

KB Article link: How do I work around the href JavaScript issue in Browser Automations? : (freshdesk.com)

------------------------------
Athiban Mahamathi - https://www.linkedin.com/in/athiban-mahamathi-544a008b/
Technical Consultant,
SimplifyNext,
Singapore
------------------------------

Original Message:
Sent: 08-02-2023 14:23
From: Terence Toledo
Subject: Invoke Javascript not working because of Content Security Policy

Hello, I would like to ask for help or a workaround for an issue I am facing. I have created a JavaScript Fragment to be added to a web app/page. However, when I invoke the script, I receive the following message in the developer tools console window: "main.js:829 Refused to execute inline script because it violates the following Content Security Policy directive: 'script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules'". It seems that my code is being blocked from execution.

Interestingly, this problem does not exist in the web browser in my development environment. I am wondering if there is any workaround to bypass the Content Security Policy?

------------------------------
Terence Toledo
------------------------------