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
Since there are many browser extensions (and also some ISPs) which inject scripts and styles into my web application, which results into errors, I use a restrictive CSP setup, which bans inline code, evals, etc.
Unfortunately, to be able to use the Sentry dialog for bug reporting, I need to set "unsafe-inline" for "style-src-elem", because it uses inline styles, which openes a door for errors.
Motivation
My motivation is, to prevent injected code into my webapp as much as possible. To prevent errors, which are triggered by browser extensions and ISPs.
Additional Context
I'm using JavaScript and the following call, to open the report dialog:
Summary
Since there are many browser extensions (and also some ISPs) which inject scripts and styles into my web application, which results into errors, I use a restrictive CSP setup, which bans inline code, evals, etc.
Unfortunately, to be able to use the Sentry dialog for bug reporting, I need to set "unsafe-inline" for "style-src-elem", because it uses inline styles, which openes a door for errors.
Motivation
My motivation is, to prevent injected code into my webapp as much as possible. To prevent errors, which are triggered by browser extensions and ISPs.
Additional Context
I'm using JavaScript and the following call, to open the report dialog:
The text was updated successfully, but these errors were encountered: