Closed Bug 1725762 Opened 4 years ago Closed 4 years ago

Open in New Container Tab -> No Container: does not work (for Instagram)

Categories

(Firefox :: Untriaged, defect)

Product:
Firefox
Component:
Untriaged
Version:
Firefox 91
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: ardeshireo, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0

Steps to reproduce:

  • Opened instagram.com. It was in Personal Container (the blue bar above it)
  • I wanted it on No Container
  • I right click on the tab, press Open in New Container Tab -> No Container
  • It re-opens in a new Personal container (the blue bar again)
  • I repeat it multiple times, it does not work, I close FireFox and re-open it, it does not work, I remove everything in developer tools -> Storage section and try again, it does not work.

Aha! I forgot to mention that I have removed the Facebook Container extension from my Firefox

The same thing happens for accounts.google.com/... so I'm not sure if it is related to me removing Facbook Container extension

Hi Ardeshir81!
Please if you have some time, could you add the expected result for your action? You can follow this guideline: https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html
Also, could you try this issue on latest Nightly version and tell us your inout? You can download it from here: https://nightly.mozilla.org/

I have tried to follow the steps mentioned using the latest version of Nighlty 93.0a1 on Ubuntu 20.4

  • Opened Instagram.com in a Personal Container
  • Right-click on the tab and select "Open in New Container Tab -> No Container"

Actual result:
A new Tab with Instagram.com was opened without Container
Note: The result was the same with or without the "Multi-Account Container" extension installed.

Flags: needinfo?(ardeshireo)

Hi Marcela. Thanks for your time. I had a rough time last night.

Last nigh immediately after I got update E-Mail for this bug, I came here, read your comment, installed Firefox nightly (93.0a1 (2021-08-24) (64-bit)), signed into my account to sync everything, everything was synced, i waited a minute to make sure everything in background is synced as well, then I opened instagram.com, but it wasn't in Personal Container, (which I expected to be, because I was in sync), I did right click on it and pressed Open in a new Personal Container, it was opened, but later when I closed and opened Firefox nightly again, instagram.com was not in a Personal Container. Even if in the same window I opened a new tab and go to instagram.com, it wouldn't open in a new container. Open in a new container worked only once! So I did not get to reproduce the issue on nightly. (maybe we can tell there is an issue that it does not persist to open a personal website always in a personal container. I remember when containers were first introduced, Firefox used to ask me whether to always open a tab in a specific container or not and I always responded yes)

Then bad things started to happen. I came to this Firefox (the normal stable Firefox, 91.0.1 (64-bit) Mozilla Firefox for Ubuntu canonical - 1.0) to write my experience here. I started writing, one paragraph into writing a few of my tabs were immediately closed, including this one. (I guess the tabs that were closed were the tabs that I have opened after I opened Firefox Nightly for the first time and started to sync, but I'm just guessing). After that from last night until now, All my container data are lost. instagram.com and gmail.com no longer open in Personal Container by default. souncloud.com does not open in music container by default, etc... . (And of course because of that I had to re-login to them again)

And worse thing I noticed today is that in my normal stable Firefox I no longer have Open in a new Container in my menu. Which is really strange. So I can not get to reproduce the issue or even use the feature on my normal Firefox now.

The things I experienced are for a separate issue, I just story-telled them here. If I could, later, I will open (a) separate issue(s) for them. I'm not sure if they are issues or just normal in-stabilities of having Firefox nightly (alongside stable Firefox)

And in the next comment I'll try to do what you asked for this issue.

Just an addition to the above comment: my ctrl+tab key combination used to switch between the last and current tab. But after the things I described, today it just consecutively traverses all the tabs (like the old behavior or chromium's behavior)

Thank you Ardeshir81 for the reply. I'm sorry to read that the test did not go well.
Perhaps in the past "Open In Personal Container" was chosen after "Remember my decision for this site" checkbox was checked for Instagram.
Can you try to do these steps and tell us your input?
Steps:
. Open the Multi-Account Containers add-on icon.
. Click on Manage Containers.
. Click on Personal container and click on "Manage Site list... " link.
. Delete the www.instagram.com.
. Open a new Tab.
. Click on the Multi-Account Containers add-on icon and chose Personal container.
. Enter www.instagram.com
. Right-click on the Instagram Tab and select "Open in New Container Tab - No Container".
Expected result: Instagram should open in a No Container tab.
Actual result: Instagram is opened in a No Container tab.

Flags: needinfo?(ardeshireo)

Thanks @Mercela. Yep that worked.Actually after I removed instagram.com from Personal list, I could open instagram.com in no container. There was no need for the last 3 steps you mentioned.

Thanks for the update. I'll close this Resolved WFM based on your comment. Please feel free to reopen it if still happens the same. Also you can add a new issue if you can still reproduce the sync issues mentioned in the comment #4

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME

Thanks Mercela. My problem is resolved. But from User Interface/Experience point-of-view is that the norm ? the only way to remove something from container is through that menu right? I can't just open it in a new container and expect it to automatically open on that container from now on?

That is by intention right?

You need to log in before you can comment on or make changes to this bug.