Caută ajutor

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Află mai multe

Container tabs not confirming any more

  • 1 răspuns
  • 0 au această problemă
  • 7 vizualizări
  • Ultimul răspuns de Ryan Johnson

more options

I have been using container tabs to juggle my corporate and personal github accounts. Until very recently, clicking a link from another app (email, etc) would start to open a new tab and then pop up a dialog asking me to confirm which container to use (see first attachment).

Unfortunately, now when I click on links it just loads straight to my "OSS github" container, which naturally produces a 404 error because my personal github account doesn't have access to the corporate repo (see second attachment).

At first, I thought I had accidentally clicked the "remember my decision" box. But the confirmation dialog still works if I open a new tab and paste the link in the address bar. It just doesn't work when other apps try to open a link in Firefox.

Is the new behavior intentional? Or did something accidentally break?

I have been using container tabs to juggle my corporate and personal github accounts. Until very recently, clicking a link from another app (email, etc) would start to open a new tab and then pop up a dialog asking me to confirm which container to use (see first attachment). Unfortunately, now when I click on links it just loads straight to my "OSS github" container, which naturally produces a 404 error because my personal github account doesn't have access to the corporate repo (see second attachment). At first, I thought I had accidentally clicked the "remember my decision" box. But the confirmation dialog still works if I open a new tab and paste the link in the address bar. It just doesn't work when other apps try to open a link in Firefox. Is the new behavior intentional? Or did something accidentally break?
Capturi de ecran atașate

Soluție aleasă

Update: It seems to be working again after updating Firefox from 132.0.0 to 132.0.1.

Citește acest răspuns în context 👍 0

Toate răspunsurile (1)

more options

Soluție aleasă

Update: It seems to be working again after updating Firefox from 132.0.0 to 132.0.1.

Te-a ajutat?

Adresează o întrebare

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.