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.

Sign up for GitHub

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

Jump to bottom

Add a Content Security Policy and load the chrome:// JS in an alternate way #77

Open

tomrittervg opened this issue Aug 30, 2021 · 0 comments

tomrittervg commented Aug 30, 2021 •

edited

We've worked around this for now in a pretty safe way; so resolving this is not urgent, but I want to have a bug on file to reference.

As described in https://bugzilla.mozilla.org/show_bug.cgi?id=1727803; about:sync triggers a Debug Assertion because it lacks a sufficiently tight CSP.

It also loads Javascript via a data: url; and it would be ideal if it could somehow load it via a chrome:// or resource:// URI.

Blocks https://bugzilla.mozilla.org/show_bug.cgi?id=1728122

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