Skip to content
This repository has been archived by the owner on Nov 17, 2017. It is now read-only.

Privacy Badger is not compatible with multiprocess Firefox (e10s) #208

Closed
cpeterso opened this issue Aug 29, 2014 · 24 comments
Closed

Privacy Badger is not compatible with multiprocess Firefox (e10s) #208

cpeterso opened this issue Aug 29, 2014 · 24 comments
Assignees
Milestone

Comments

@cpeterso
Copy link
Contributor

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

@cooperq cooperq added the bug label Aug 30, 2014
@cooperq cooperq modified the milestone: 0.2 Sep 12, 2014
@EuphoricEuler
Copy link

Installed Privacy badger on the current FF Nightly, Addon does not show up in urlbar and toolbar.
Nightly build: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:36.0) Gecko/20100101 Firefox/36.0 ID:20141114030206 CSet: 7f0d92595432
Privacy Badger 0.2.3

@EuphoricEuler
Copy link

Also documented in the bugzilla bug mentioned by cepterso ( comment 1 )

@rugk
Copy link

rugk commented Aug 21, 2015

Any news here?
Just FYI there is a helpful blog post about the future of developing add-ons (including e10s and add-on signing): https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/

@cooperq
Copy link
Contributor

cooperq commented Aug 24, 2015

no news. needs to be worked on. there are other things that need to be worked on more.

@SylvainMartel
Copy link

Any news on this? e10s is now enabled by default in FF49 and Privacy Badger isn't working with e10s yet.

@wshanks
Copy link

wshanks commented Aug 8, 2016

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 web-ext lint on the Chrome version and got the output below. I think it is all warnings that can be ignored except the messages about incognito and the permissions for privacy and unlimitedStorage. I'm not sure about privacy (could not find any mention of it in the WebExtensions documentation), but the chrome incompatibilities page on MDN states that Firefox does not support incognito: split or unlimitedStorage, so those would need to worked around.

Code                    Message                             Description                                                   File            Line   Column
MANIFEST_JSON_INVALID   "/incognito" should match pattern   See https://mzl.la/1ZOhoEN (MDN Docs) for more information.   manifest.json                
                        "^spanning$"                                                                                                                   
NOTICES:

Code                     Message                                    Description                                                                              File                                Line   Column
MANIFEST_UNUSED_UPDATE   The "update_url" property is not used by   The "update_url" is not used by Firefox in the root of a manifest; your add-on will be   manifest.json                                    
                         Firefox.                                   updated via the Add-ons site and not your "update_url". See: https://mzl.la/25zqk4O                                                       
KNOWN_LIBRARY            Known JS library detected                  JavaScript libraries are discouraged for simple add-ons, but are generally accepted.     lib/underscore-min.js                            
KNOWN_LIBRARY            Known JS library detected                  JavaScript libraries are discouraged for simple add-ons, but are generally accepted.     lib/jquery-ui/js/jquery-1.10.2.js                
WARNINGS:

Code                     Message                                       Description                                                                           File                                Line   Column
MANIFEST_PERMISSIONS     /permissions: Unknown permissions             See https://mzl.la/1R1n1t0 (MDN Docs) for more information.                           manifest.json                                    
                         "unlimitedStorage" at 7.                                                                                                                                                             
MANIFEST_PERMISSIONS     /permissions: Unknown permissions "privacy"   See https://mzl.la/1R1n1t0 (MDN Docs) for more information.                           manifest.json                                    
                         at 1.                                                                                                                                                                                
UNADVISED_LIBRARY        Unadvised 3rd-party JS library                Your add-on uses a JavaScript library we do not recommend. Read more:                 lib/jquery-ui/js/jquery-1.10.2.js                
                                                                       https://bit.ly/1TRIyZY                                                                                                                 
UNEXPECTED_GLOGAL_ARG    Unexpected global passed as an argument       Passing a global as an argument is not recommended. Please make this a var instead.   lib/compat.js                       30     17    
FLAGGED_FILE_EXTENSION   Flagged file extensions found                 Files were found that are either unnecessary or have been included unintentionally.   scripts/makezip.sh                               
                                                                       They should be removed.                                                                                                                
FLAGGED_FILE_EXTENSION   Flagged file extensions found                 Files were found that are either unnecessary or have been included unintentionally.   scripts/setup_travis.sh                          
                                                                       They should be removed.                                                                                                                
FLAGGED_FILE_EXTENSION   Flagged file extensions found                 Files were found that are either unnecessary or have been included unintentionally.   scripts/run-nightly.sh                           
                                                                       They should be removed.                                                                                                                
FLAGGED_FILE_EXTENSION   Flagged file extensions found                 Files were found that are either unnecessary or have been included unintentionally.   scripts/makecrx.sh                               
                                                                       They should be removed.                                                                                                                
TABS_GETSELECTED         "tabs.getSelected" is deprecated or           This API has been deprecated by Chrome and has not been implemented by Firefox.       src/popup.js                        96     5     
                         unimplemented                                                                                                                                                                        
TABS_GETSELECTED         "tabs.getSelected" is deprecated or           This API has been deprecated by Chrome and has not been implemented by Firefox.       src/popup.js                        521    3     
                         unimplemented                                                                                                                                                                        
TABS_GETALLINWINDOW      "tabs.getAllInWindow" is deprecated or        This API has been deprecated by Chrome and has not been implemented by Firefox.       src/options.js                      95     7     
                         unimplemented                                                                                                                                                                        
TABS_GETSELECTED         "tabs.getSelected" is deprecated or           This API has been deprecated by Chrome and has not been implemented by Firefox.       src/options.js                      418    3     
                         unimplemented                                                                                                                                                                        
FLAGGED_FILE_EXTENSION   Flagged file extensions found                 Files were found that are either unnecessary or have been included unintentionally.   tests/run_selenium_tests.sh                      
                                                                       They should be removed.                                                                                                                
FLAGGED_FILE_EXTENSION   Flagged file extensions found                 Files were found that are either unnecessary or have been included unintentionally.   scripts/justrun.sh                               
                                                                       They should be removed.                                                                   

@cooperq
Copy link
Contributor

cooperq commented Aug 11, 2016

@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.

@maximus5959
Copy link

Glad this is being worked on.

@Mikaela
Copy link

Mikaela commented Sep 17, 2016

That work is being tracked here: EFForg/privacybadger#845

Does this still apply? That pull request seems to be merged and Milestone
Web Extensions API
closed.

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).


My loaded Firefox addons

@mirh
Copy link

mirh commented Sep 17, 2016

It may be as well we just lack the "multiprocess" permission then.

@wshanks
Copy link

wshanks commented Sep 17, 2016

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 make xpi, and then uploaded the xpi to Mozilla for signing. After that, I could install it into the current version of Firefox and it seemed to be blocking trackers as normal. I had to force enable multiprocess (https://wiki.mozilla.org/Electrolysis#Force_Enable) to get it to activate with Privacy Badger installed.

@cooperq
Copy link
Contributor

cooperq commented Sep 20, 2016

@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.

@Mikaela
Copy link

Mikaela commented Sep 20, 2016

If I understood correctly, that is also being worked on Firefox Addons mailing list.

valinta_260

Source for Telegram users

@rugk
Copy link

rugk commented Oct 2, 2016

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

Examples: https://github.com/rpl/webextensions-examples/tree/examples/hybrid-addons-native-messaging/embedded-webextension-native-messaging

@Mikaela
Copy link

Mikaela commented Nov 17, 2016

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.

@wshanks
Copy link

wshanks commented Nov 18, 2016

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.

@cooperq
Copy link
Contributor

cooperq commented Nov 26, 2016

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.

@Hasshu
Copy link

Hasshu commented Jan 13, 2017

Watch out for the next version, hopefully in mid december.

December of what year?

@mirh
Copy link

mirh commented Jan 13, 2017

Since like December 15.

@wshanks
Copy link

wshanks commented Jan 14, 2017

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.

@Hasshu
Copy link

Hasshu commented Jan 14, 2017

@mirh You ain't no fun at all. :/

@willsALMANJ Indeed, looks like this place is all but abandoned.

@mirh
Copy link

mirh commented Jan 14, 2017

It's not fun. That's when newer version has been released. Use it.
They should remove/port this bug tracker.

@Hasshu
Copy link

Hasshu commented Jan 14, 2017

It's not fun.

Uh... Never mind.

That's when newer version has been released. Use it.

Figures. Actually, I have it installed. I just wasn't sure whether it's the one with initial e10s support.

They should remove/port this bug tracker.

This.

@cooperq
Copy link
Contributor

cooperq commented Jan 18, 2017

Indeed the current version of privacy badger is compatible with E10S. Thanks.

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

No branches or pull requests

10 participants