“Facebook Container” container remains available even after removing the extension

[acornestean]

Before submitting a bug report

• I updated to the latest version of Multi-Account Container and tested if I can reproduce the issue
• I searched for existing reports to see if it hasn't already been reported

Step to reproduce

1. Install the 8.1.0 version of Multi-Account Containers
2. Open the Multi-Account Containers pop-up and notice there is no Facebook container in the list of available containers
3. Install Facebook Container (https://addons.mozilla.org/en-US/firefox/addon/facebook-container/)
4. Open the Multi-Account Containers pop-up and notice there is a Facebook container entry in the list of available containers
5. Remove Facebook Container
6. Open the Multi-Account Containers pop-up and notice there still is a Facebook container entry in the list of available containers which still retains functionality in the sense that tabs can be opened in said container

Actual behavior

Once Facebook Container is removed, the corresponding container is still available in Multi-Account Containers.

Expected behavior

Once Facebook Container is removed, the corresponding container should also be removed from Multi-Account Containers.

Additional informations

Provide a copy of Troubleshooting Information page (optional)

No response

[dannycolin]

@maxxcrawford @groovecoder Maybe this is something we might want to fix in Facebook Container instead of Multi-Account Container. What do you think?

[geedogz]

Same issue here. All containers used on this addon remain after I either disable or delete the addon also.

Also, firefox's own containers have been removed in the latest version. Does anyone know why?

[kurahaupo]

Firstly, if anything this is a bug in the Facebook container plug-in, not this one.

Secondly, what if the user had done things in a different order:

1. add the MAC plug-in; then (maybe a lot later)
2. using MAC, create their own container and name it "Facebook"; then
3. add the "Facebook container" plug-in; then
4. do some testing that triggers the "Facebook" plug-in; then
5. remove the "Facebook container" plug-in?

Would you then still expect the container named "Facebook" created in MAC to be removed during the removal of the "Facebook container" plug-in?

[gpetrioli]

Not sure if this is only a "Facebook container" bug or if it is related to this extension as well, but after i remove this extention (while keeping the facebook one) i can do the following

the right click on the "+ open new tab" button shows containers

and if you go to "Manage containers" from that menu you get to

So it seems like these two extensions share some things and they do not clean-up after their own additions.

[kurahaupo]

@gpetrioli to my mind, this would be like hiring a builder to add an extension to your house, and then expecting them tear it down when they leave.

Add-ons are container managers, not containers themselves, and they don't "own" individual containers.

I wonder if this distinction could be improved in the descriptions that people see prior to installing add-ons?