Getting "Open this site in your assigned Container" even after setting remember my decision

[AztrexDX]

Before submitting a bug report

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

Step to reproduce

1- download latest version of firefox 2- Download extension 3- After visiting a site through container like links of google search again try to open the link will get "Open this site in your assigned Container" 4- After setting remember my decision still getting prompt to "Open this site in your assigned Container"

Actual behavior

should not get this prompt as earlier version.

Expected behavior

1- After remembering this decision it should not again give prompt 2- Like earlier version there should be no prompt. It was more easier. It is too much effort to keep setting this in this version Don't know what caused this either updated version of firefox or plugin

Additional informations

No response

Provide a copy of Troubleshooting Information page (optional)

No response

[dannycolin]

What buttons do you click on? "Open in current tab" or "Open in Shopping container"?

[FernandAdam]

I think I have the same bug. The remember box is checked:

• When I click on "Open in current tab" it will ask again if I try to open the site in a new Tab.
• When I click on "Open in ____ Container" it works. The extension always opens the site directly in the assigned Container.

[achernyakevich-sc]

I think I have the same bug. The remember box is checked:

* When I click on "Open in current tab" it will ask again if I try to open the site in a new Tab.

* When I click on "Open in ____ Container" it works. The extension always opens the site directly in the assigned Container.

@FernandAdam , @AztrexDX This is exactly the way how it was designed to work. Yes, it is misleading and there are plenty of issues with the same "user expectations of MAC behavior that are not matching to current functionality implementation".

I would propose you to visit #2294 and:

• check issue description about how it is proposed to avoid misleading by changing UI.
• vote for the issue.
• check thread for linked issues to see that this issue is just another one duplicate.
• close this issue as duplicate.

[magmax]

Maybe this issue is duplicating #2126 , right?