content-security-policy: unsafe-eval

[ysantosa]

It seems unsafe-eval is needed for CPS (Content-Security-Policy) for the library to be used.

Is this the case ? Is there a way not to require 'unsafe-eval' ?

Particularly in environment where developers may not have the ability / privileges to alter the Response Header of the server serving the library.

Thanks !

[Lech Kulikowski]

Hello,

Could you explain your issue in more details?

Thank you.