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

Not obvious when accidentally enabled. #5

Open
imthought opened this issue May 7, 2020 · 2 comments
Open

Not obvious when accidentally enabled. #5

imthought opened this issue May 7, 2020 · 2 comments

Comments

@imthought
Copy link

imthought commented May 7, 2020

When it is enabled the icon goes gray, but if you miss that all you get are content security policy errors in Firefox for all JS scripts. It would be great if when it was enabled it output a console log to tell a person it is that it is turned on in the same place it will create errors. That way id it is accidentally tripped it or set it some time ago on a site that the user is going back they don't end up ripping out their hair trying to figure out why they are getting CSP errors.

@meetDeveloper
Copy link
Owner

@imthought Will fix this today.

@goozak
Copy link

goozak commented Feb 22, 2021

Just spent an hour pulling my hair out with this! Finally decided to try a new Firefox profile and when that worked, went thru my extensions to find the culprit.

The worst part is that it's not the first time... 😭

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

No branches or pull requests

3 participants