Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Report CSP errors? #3013

Closed
fregante opened this issue Mar 23, 2022 · 2 comments
Closed

Report CSP errors? #3013

fregante opened this issue Mar 23, 2022 · 2 comments

Comments

@fregante
Copy link
Contributor

fregante commented Mar 23, 2022

Interesting global event, maybe we can handle it similarly to uncaught errors:

@twschiller This might be a partial answer to “how do we know why a request failed”?

@twschiller
Copy link
Contributor

twschiller commented Mar 24, 2022

Worth a shot, especially since we've been having network errors.

If we add this, we should only add on our extension pages. Would be way too noisy in the content script (b/c I think we'd pick up CSP errors from the host page)

Potentially could also combine with https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/report-uri, but that wouldn't give user-level information

Related: #3020

@twschiller
Copy link
Contributor

Potentially related: w3c/webextensions#197

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

2 participants