Remove unsafe-eval requirement from content security policy headers

The trengo widget in order to work properly requires "unsafe-eval" header which is a really unsafe policy for modern websites. It would be really amazing if this could be improved as my team is considering other options just for this thing alone, depite Trengo being an amazing solution.

 

Official documentation: https://developers.trengo.com/docs/content-security-policy

Reply Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
Like Follow
  • 6 mths agoLast active
  • 2Views
  • 1 Following