Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Container tabs not confirming any more

  • 1 risposta
  • 0 hanno questo problema
  • 7 visualizzazioni
  • Ultima risposta di 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?
Immagini allegate

Soluzione scelta

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

Leggere questa risposta nel contesto 👍 0

Tutte le risposte (1)

more options

Soluzione scelta

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

È stato utile?

Richiedi supporto

Bisogna accedere al proprio account per rispondere nelle discussioni. Se non si possiede ancora un account, inserire una nuova richiesta.