Trying to trigger a click (and maybe other events too) on a website that has some level of Content-Security-Policy restricting 'unsafe-eval', the test cannot be run due eval() called somewhere inside selenium-ide.
Why it requires eval()? Could this be solved by replacing code that does not require eval()?
This is due to browser extension limitations. As of now you can work around it by using Selenium IDE v4 or side-runner to execute your recorded tests on websites with content security policy limitations.
š Bug Report
Trying to trigger a click (and maybe other events too) on a website that has some level of Content-Security-Policy restricting 'unsafe-eval', the test cannot be run due eval() called somewhere inside selenium-ide.
Why it requires eval()? Could this be solved by replacing code that does not require eval()?
To Reproduce
Error because Selenium called eval() somewhere that is not allowed by the website CSP.
Expected behavior
Test runs without error.
Project file
Environment
OS: macOS (x64 and aarch64) Selenium IDE Version: 3.17.4 Browser: Firefox Browser Version: Firefox 115.16.1esr (64-bit), Firefox 131.0.3 (aarch64)