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
Privacy Badger broken on Chrome Dev #901
Comments
I can reproduce this. |
I suppose this could be the problem, from this chrome issue:
|
I can't find a way to debug this so it's pretty opaque. Privacy Badger does not use the filesystem api so I don't see how it could be changing its own files (which causes the issue in my last comment). I don't think it is this zero length files bug because I couldn't find any zero length files. https://bugs.chromium.org/p/chromium/issues/detail?id=399251#makechanges |
Maybe we are violating the default Content Security Policy we get by having
But these rules don't apply to content scripts. Maybe I missed something. |
I am seeing this in Chrome Beta as well (53.0.2785.80 beta (64-bit)), on MacOS El Capitan (10.11.6), with Privacy Badger 2016.08.29. Notably, I do NOT see the same issue with HTTPS Everywhere. |
We have a fix for this now which will be in the next release. For now |
Setting extension content verification to 'enforce' unfortunately doesn't fix the issue for me. |
So it turns out this is an issue in chrome, the chrome devs are aware of it and are working on a fix now. Follow the issue here: https://bugs.chromium.org/p/chromium/issues/detail?id=643814 |
Privacy Badger is reported as 'corrupt' on Chrome Dev (my exact version was 54.0.2837.0 dev-m (64 bit)) but works fine on the stable channel. I've tested on two different browsers. I have not tested the Beta or Canary channels. Clicking "Repair" reinstalls the extension with the same error.
This does not occur with any other extensions.
This occurs even when "Extension content verification" is set to Bootstrap in chrome://flags.
This issue also occurs with HTTPS Everywhere and has been reported on its GitHub as well.
The text was updated successfully, but these errors were encountered: