• Multi-Account Containers Version: 8.0.1
• Operating System + Version: Windows 10 Pro - 10.0.19043 Build 19043
• Firefox Version: 94.0.1 (64-bit)
• Other installed Add-ons + Version + Enabled/Disabled-Status: Facebook Container extension 2.3.1 true @contain-facebook

Actual behavior

"https://support.mozilla.org/en-US/" opens in the current container (container a) regardless if it is set to be forced to open in another container (container b), and/or regardless of the current one (container a) being limited to domains not including "support.mozilla.org".

Expected behavior

"https://support.mozilla.org/en-US/" opens without a container if the current one is limited, or it opens in its assigned container if it has been allocated to one

Steps to reproduce

1. Create a container for the "duckduckgo.com" domain
2. Create a container for the "support.mozilla.org" domain
3. From "duckduckgo.com" search for, and select to open "support.mozilla.org" using the results
4. "https://support.mozilla.org/en-US/" will open in the duckduckgo container

Notes

None

I noticed this too a whole year later. I have Google in its own container and I ran a few search results that pulled up support.mozilla.org. I clicked on the following links:

1. Support.mozilla.org: Somehow opens in the same Google only container.
2. Github link: No specific container
3. Reddit link: My social media container

The first link, (support.mozilla.org) opens in the wrong container clearly.

• Multi-Account Containers Version 8.0.9
• Firefox 107.0.1
• Windows 10 Pro 19045.2311

@Sea-Worker9552 Did you enable "Limit to designated sites" in your Google container?

Hi, y'all, another one for this issue. ( sorry, @dannycolin ! 😩 )

Cause Thoughts

I believe that this might have something to do with the 'privileged' status that mozilla.org and firefox.com hold. I know that they both affect how noscript works ... but I'm not entirely sure how they would related to MAC. Either way, it feels like the issue here.

I've noticed that there appears to have been some change recently that allows some Mozilla sub-domains to be assigned to MACs, could it be that this implementation was potentially a bit borked? 🤔

Replicated Incident - Using MAC Named "Search"

I have seen this happen a few times, but I am presenting two recent occurrences here.

If I try to open any other site it works as it should or directly to no container at all.

First Occurrence - Search MAC

This was the first example which I saw on version 122.0a1 following this series of events:

1. Searched for the following on startpage opened correctly in the Search MAC: firefox kiosk mode

2. Tapped the first result pictured below

3. That opened in a Search MAC which should be restricted to the sites mentioned in the Additional Information section below

Second Occurrence - No MAC

The issue persisted after updating to 123.0a1 with the following events as evidence:

1. I quickly created a MAC called Mozilla (no screenshot)
2. I opened a new tab in the Mozilla MAC to this address
3. I set that to always open in this MAC
4. I opened the settings to about:preferences#search
5. I tapped the 'Learn more' link next to the option which I cannot uncheck ( 😠 )
6. This opened in no container

This happened whether the new Mozilla MAC was set to limit to sites or not.

Additional Information

Operating System

Windows 11 64-bit 22H2

Browser

Nightly Version 122.0a1 (2023-12-14) (64-bit)
Version 123.0a1 (2023-12-19) (64-bit)

Multi-Account Containers Settings

The container is set to Limit to Designated Sites:

The sites it is limited to are:

1. duckduckgo.com
2. eu-browse.startpage.com
3. www.startpage.com

@Sea-Worker9552 Did you enable "Limit to designated sites" in your Google container?

@dannycolin Jeez I must've missed this one last year. I confirmed limit designed sites is checked in my Google container. That's why I can open a new tab and open support.mozilla.org in a brand new tab with no container. But when I click on a result from Google that takes me to support.mozilla.org, it opens in my Google container.

Issue still happens on FF 121 on MacOS 14.2.1

https://www.youtube.com/watch?v=W4qKql2gDVA

You can see in this video in clicking on the links, the Mozilla links trigger an opening in the same container as my search (Google container). However when I manually open a new tab and paste that link in, it does not open in my Google tab. Other non-Mozilla links open in a non-container tab.

Thought that I would just confirm that this behaviour is still occurring.

That's not being added as a nag, just to say that it is not a one-off.