epam / epam/Indigo

Content Security Policy - "unsafe-eval"

Open
#567 1 comment 0 reactions 1 assignee Claimed by @mkviatkovskii View on GitHub
Dominant language
C++
Stars
406
Forks
134
Avg merge
2d 11h
Merged PRs (30d)
24

Description

*Steps to Reproduce*
Add a CSP (in your html entry file) that doesn't allow for "unsafe-eval"

*Expected behavior*
Not throw a CSP error

*Actual behavior*
Throws a CSP error

Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script
Additional context
I've tracked this down to ketcher-standalone/src/generate/libindigo.js line 1230. Specifically new Function will cause this.

Don't have enough context to make a change to this but essentially new Function should go away otherwise CSP won't let it run.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.