You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are encountering issues rendering our form when implementing Content Security Policy (CSP) without unsafe-eval. As per our security guidelines, we are required to remove the unsafe-eval directive from the script-src policy.
Issue Details
When unsafe-eval is removed from the CSP, the form fails to render correctly. This appears to be related to the use of libraries or frameworks that rely on eval-like functionality, which is restricted by CSP policies. The affected components are critical to our application, and the error prevents users from interacting with the form.
Request for Support
We seek guidance on:
Workarounds: Any suggested approaches to handle CSP restrictions without enabling unsafe-eval.
Library Updates: Is there a roadmap to eliminate the reliance on eval in the library?
We are encountering issues rendering our form when implementing Content Security Policy (CSP) without unsafe-eval. As per our security guidelines, we are required to remove the unsafe-eval directive from the script-src policy.
Issue Details
When unsafe-eval is removed from the CSP, the form fails to render correctly. This appears to be related to the use of libraries or frameworks that rely on eval-like functionality, which is restricted by CSP policies. The affected components are critical to our application, and the error prevents users from interacting with the form.
Request for Support
We seek guidance on:
Workarounds: Any suggested approaches to handle CSP restrictions without enabling unsafe-eval.
Library Updates: Is there a roadmap to eliminate the reliance on eval in the library?
Originally posted by @expertprincekumar in #5961 (comment)
The text was updated successfully, but these errors were encountered: