Firefox Multi-Account Containers

Embedded Web Extension to build Containers as a Firefox Test Pilot Experiment and Shield Study to learn:

• Will a general Firefox audience understand the Containers feature?
• Is the UI as currently implemented in Nightly clear or discoverable?

For more info, see:

• Test Pilot Product Hypothesis Document
• Shield Product Hypothesis Document

Requirements

• node 7+ (for jpm)
• Firefox 53+

Development

Web Extension Development

Since Firefox 57, this extension can now be run without any of the legacy components that were previously needed.

1. Install web-ext with npm
2. cd webextension; web-ext run -f Nightly

This will work in other builds of Firefox however certain features won't work and you will need to manually flip preferences to enable containers. All other sections of this guide talk about using the legacy setup with jpm.

Legacy Development

Development Environment

Add-on development is better with a particular environment. One simple way to get that environment set up is to install the DevPrefs add-on. You can make a custom Firefox profile that includes the DevPrefs add-on, and use that profile when you run the code in this repository.

1. Make a new profile by running /path/to/firefox -P, which launches the profile editor. "Create Profile" -- name it whatever you wish (e.g. 'addon_dev') and store it in the default location. It's probably best to deselect the option to "Use without asking," since you probably don't want to use this as your default profile.

2. Once you've created your profile, click "Start Firefox". A new instance of Firefox should launch. Go to Tools->Add-ons and search for "DevPrefs". Install it. Quit Firefox.

3. Now you have a new, vanilla Firefox profile with the DevPrefs add-on installed. You can use your new profile with the code in this repository like so:

Run the .xpi file in an unbranded build

Release & Beta channels do not allow un-signed add-ons, even with the DevPrefs. So, you must run the add-on in an unbranded build:

1. Download and install an un-branded build of Firefox
2. Download the latest .xpi from this repository's releases
3. Run the un-branded build of Firefox with your DevPrefs profile
4. Go to about:addons
5. Click the gear, and select "Install Add-on From File..."
6. Select the .xpi file

Correct prefs

Whilst this is still using legacy code to test you will need the following in your profile:

Change the following prefs in about:config:

• extensions.legacy.enabled = true
• xpinstall.signatures.required = false

Run the TxP experiment with jpm

1. git clone git@github.com:mozilla/testpilot-containers.git
2. cd testpilot-containers
3. npm install
4. ./node_modules/.bin/jpm run -p /Path/To/Firefox/Profiles/{junk}.addon_dev -b FirefoxBeta (where FirefoxBeta might be: ~//obj-x86_64-pc-linux-gnu/dist/bin/firefox or ~//firefox)

Check out the Browser Toolbox for more information about debugging add-on code.

Building .xpi

To build a local testpilot-containers.xpi, use the plain jpm xpi command, or run npm run build.

Signing an .xpi

To sign an .xpi, use jpm sign command.

Note: You will need to be an author on the AMO add-on.

Testing

TBD

Distributing

TBD

Links

• Licence
• Contributing
• Code Of Conduct