Firefox Multi-Account Containers lets you keep parts of your online life separated into color-coded tabs that preserve your privacy. Cookies are separated by container, allowing you to use the web with multiple identities or accounts simultaneously.
![]() Hypothesis: On receiving onChanged event of browser.storage.sync, sync will try to _merge_ the container data and backup the merged data. One of the merging process is called reconcileSiteAssignments in which sync will remove assigned site form the delete site list. On each removal sync will tell assignManager, the one who hold container data locally, to remove it as well. In turn the assignManager will remove *and then* tell sync to backup the data. This causes the backup process in sync to be invoked multiple times, one from the sync process and one for each of removed assigned site list. To make matters worse, the backup from removal of assigned site list will run in parallel from each others. This might fixes #1691. |
||
---|---|---|
.github | ||
bin | ||
data | ||
docs | ||
src | ||
test | ||
.env | ||
.eslintignore | ||
.eslintrc.js | ||
.gitignore | ||
.htmllintrc | ||
.jpmignore | ||
.stylelintrc | ||
.travis.yml | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
icon.png | ||
LICENSE.txt | ||
package.json | ||
README.md |
Multi-Account Containers
The Firefox Multi-Account Containers extension lets you carve out a separate box for each of your online lives – no more opening a different browser just to check your work email! Learn More Here
Available on addons.mozilla.org
For more info, see:
Requirements
- node 7+ (for jpm)
- Firefox 57+
Development
npm install
./node_modules/web-ext/bin/web-ext run -s src/
Testing
npm run test
or
npm run lint
for just the linter
There is a timeout test that sometimes fails on certain machines, so make sure to run the tests on your clone before you make any changes to see if you have this problem.
Distributing
Make the new version
- Bump the version number in
package.json
andmanifest.json
- Commit the version number bump
- Create a git tag for the version:
git tag <version>
- Push the tag up to GitHub:
git push --tags
Publish to AMO
npm run-script build
- Upload the
.zip
to AMO
Publish to GitHub
Finally, we also publish the release to GitHub for those followers.
- Download the signed
.xpi
from the addon versions page - Make the new release on
GitHub
- Use the version number for "Tag version" and "Release title"
- Release notes: copy the output of
git log --no-merges --pretty=format:"%h %s" <previous-version>..<new-version>
- Attach binaries: select the signed
.xpi
file
Links
Facebook & Twitter icons CC-Attrib https://fairheadcreative.com.