-
Notifications
You must be signed in to change notification settings - Fork 68
Privacy Badger is not compatible with multiprocess Firefox (e10s) #208
Comments
Installed Privacy badger on the current FF Nightly, Addon does not show up in urlbar and toolbar. |
Also documented in the bugzilla bug mentioned by cepterso ( comment 1 ) |
Any news here? |
no news. needs to be worked on. there are other things that need to be worked on more. |
added missing g-plusone button selector
Any news on this? e10s is now enabled by default in FF49 and Privacy Badger isn't working with e10s yet. |
What is your plan for the future of the Firefox SDK version of Privacy Badger? e10s support probably needs to be done by spring/summer of 2017 (just guessing when it might be turned on for everyone based on what I have seen from Mozilla), but since you already have a Chrome version it might better to put the effort into porting the Chrome extension to a Firefox WebExtension rather than updating the SDK version. I tried running
|
@willsALMANJ we are indeed working towards getting the chrome version of privacy badger compatible with web extensions. That work is being tracked here: EFForg/privacybadger#845 I have already, in that branch, fixed the issues with incognito, privacy, and unlimitedStorage. The plan is to get this version out as soon as we find a strategy to migrate the data from the jpm extension to the web extension, this will hopefully be in the next couple of months. |
Glad this is being worked on. |
Does this still apply? That pull request seems to be merged and Milestone I would be interested in the ETA for this arriving to Firefox enabling multi-process for me or at least following the development happening (if I understand anything of it). |
It may be as well we just lack the "multiprocess" permission then. |
My understanding from reading the issues is that the Chrome extension is now compatible with WebExtensions. I think the hold up is that a data migration tool for upgrading from the old Firefox SDK version to the new WebExtension version has not been created. This was mentioned in a comment above and also in this comment: EFForg/privacybadger#845 (comment) but I haven't found any follow up to it in other issues in either the Firefox or Chrome issue trackers. I don't think the WebExtension version will be pushed to Mozilla until this is taken care of. If you really wanted to do (and didn't care about keeping your old data), you could try building and signing the WebExtension version yourself. EDIT: I just tried this myself and it seemed to work fine. I cloned privacybadgerchrome, changed the gecko id in manifest.json, ran |
@willsALMANJ is correct about the reason for the holdup on this. I am working on a data migration scheme now, I plan to have the web extensions version released as soon as thats done. Hopefully in the next 3-4 weeks. |
If I understood correctly, that is also being worked on Firefox Addons mailing list. |
For migrating the data from the old extension to the web extension you may use the new hybrid extensions supported of Firefox 51: https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Embedded_WebExtensions |
Has anything happened with this issue? PrivacyBadger continues being the only addon keeping me from e10s Firefox and I think e10s would fix annoying freezing I have sometimes (even if I think I know the culprit) and it seems like no commit has referenced here and the IRC channel has been silent. I am even thinking of temporarily replacing Privacy Badger with µBlock Origin even if I would be fine with not-tracking advertisers. |
I'm not sure what the current status is, but I believe the relevant commits are here: https://github.com/EFForg/privacybadgerfirefox/commits/dataMigrate. As I said in my previous post on here, the Chrome version of Privacy Badger already works on Firefox (with e10s). The issue is providing a smooth upgrade that preserves user data. |
The very next version of Privacy Badger will be e10s compatible as we are switching to web extensions. Yay! as far as @willsALMANJ yes you are correct. Those commits are the ones providing a smooth data migration path for users. Everything is set! Watch out for the next version, hopefully in mid december. |
December of what year? |
Since like December 15. |
Yeah, this issue could be closed because the version on AMO is now compatible with multiprocess Firefox. However, I think this repo has been deprecated because PrivacyBadger now uses the Chrome version for both Chrome and Firefox. |
@mirh You ain't no fun at all. :/ @willsALMANJ Indeed, looks like this place is all but abandoned. |
It's not fun. That's when newer version has been released. Use it. |
Uh... Never mind.
Figures. Actually, I have it installed. I just wasn't sure whether it's the one with initial e10s support.
This. |
Indeed the current version of privacy badger is compatible with E10S. Thanks. |
Here is the Firefox bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1006330
If you have any questions about add-on support for multiprocess Firefox (e10s), just drop by the #e10s IRC channel on irc.mozilla.org. MDN also has a good introduction:
https://developer.mozilla.org/en-US/Add-ons/Working_with_multiprocess_Firefox
The text was updated successfully, but these errors were encountered: