Disabling and re-enabling the add-on resets the config

[cjkent]

• Is "Firefox will: Never remember history" in the Firefox Preferences/Options under "Privacy & Security > History" selected? No
• Are you using Firefox in a Private Window? No
• Can you see a grayed out but ticked Checkbox with the description "Enable Container Tabs" in the Firefox Preferences/Options under "Tabs"? No
• Multi-Account Containers Version: 6.0.0
• Operating System + Version: macOS 10.13.5
• Firefox Version: 61.0.1
• Other installed Add-ons + Version + Enabled/Disabled-Status:

Name	Version	Enabled	ID
Firefox Multi-Account Containers	6.0.0	true	@testpilot-containers
New Tab Override	14.0.2	true	newtaboverride@agenedia.com
Stylus	1.4.13	true	{7a7a4a92-a2a0-41d1-9fd7-1e92480d612d}
uBlock Origin	1.16.12	true	uBlock0@raymondhill.net
Vimium	1.63.3	true	{d7742d87-e61d-4b78-b8a1-b469842139fa}
Blank New Tab	2.0.0	false	blanknewtab@goodthings
Context Search Origin	2.1	false	{e040cf12-0537-4265-8ce0-ee195356ed60}
OneLogin for Firefox	3.4.2	false	extension@onelogin.com

Actual behavior

Container tabs configuration is reset after disabling and re-enabling the add-on

Expected behavior

Configuration is restored when re-enabling the add-on

Steps to reproduce

1. Add a new container
2. Disable the add-on
3. Enable the add-on

The new container has disappeared.

Notes

This is a horrible issue. Due to #1227 I spent a lot of effort manually hacking my config. I disabled the add-on when I was trying to diagnose an (unrelated) problem with Firefox. And when I re-enabled it my config was reset to the default.

[AdKiller]

same problem here with Firefox ESR 60. spent a lot of time configuring containers, disabled the addon temporarily to troubleshoot something and when enabled, poof everything was gone...

[HeikoAdams]

Same happens if firefox crashes and wants to restore the last session via about:sessionrestore at next startup

[qsantos]

Same

[ZombieAlex]

This is actually even worse than described. Disabling and re-enabling removes all your custom containers but does not reset @testpilot-containers/storage.js with all site assignments.

storage.js pairs domains with containers by a container ID number rather than the container's name.

The two issues combined mean that after I recreated my custom containers in a different order than they were before I'd disabled the extension, I now have domains automatically loading in the wrong container.

I'd prefer if disabling didn't remove custom containers at all. But if that's not fixable for some reason, it should definitely reset storage.js and domain assignments as well.

[Tithen-Firion]

Now with armagadd-on-2.0 this issue affected many people. Any plans to change the current behaviour?

[AdKiller]

I have a creeping feeling that after today's sh*t show with certificate signing that disabled all Firefox add-ons across all platforms, the settings of this addon will be reset again. (thankfully I have backups that I can dig out).
https://www.ghacks.net/2019/05/04/your-firefox-extensions-are-all-disabled-thats-a-bug/

Firefox containers is the best feature that Mozilla has created in a long time, and the only thing that sets it apart from Google Chrome, for now...

+ Improving Firefox containers and fixing this issue should be top priority.

[quietlystorming]

I have a creeping feeling that after today's sh*t show with certificate signing that disabled all Firefox add-ons across all platforms, the settings of this addon will be reset again.

@AdKiller You were right.

[qsantos]

When I encountered the problem, I feared that the usual proposed solution, which implied reinstalling the addons, would wipe out my containers (again). However, I managed to reactivate my addons using another approach (note that I needed to set devtools.chrome.enabled to true in about:config to access to the browser console prompt).

Nevermind, hotfix 66.0.4 did reset my containers…

[groovecoder]

See also https://bugzilla.mozilla.org/show_bug.cgi?id=1549204 for the bugzilla bug, and I'm going to start closing duplicate issues of this one.

[qsantos]

Nevermind my previous comment: 66.0.4 did reset my containers…