We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

Why does TB do mailto differently depending on state of FF that started it?

  • 1 отговор
  • 1 има този проблем
  • 3 изгледи
  • Последен отговор от pb

more options

win 7 64 bit, TB 38.5.1

This is a followup to

https://support.mozilla.org/en-US/questions/1108691

and

https://support.mozilla.org/en-US/questions/1108660

When I do an "email link" or click a "malto" in FF, if TB is already running, sometimes I get a mail compose window as I want, and sometimes I get the TB profile manager, which of course does not allow me to select the currently runnin TB profile, which is the one that I of course want.

The only difference between the two scenarios is whether FF was started with the "-no-remote" option.

I have established that TB is being started with the identical command line in both cases, so I am at a loss to understand why it behaves differently depending on how the FF that invokes it was started.

How does TB decide whether it wants to invoke the profile manager when it is already running?

For example, is there some registry value or ENV variable that FF or the OS might have set that it would look at other than the command line to start it?

The exact same TB executable is being invoked also.

Thanks.

win 7 64 bit, TB 38.5.1 This is a followup to https://support.mozilla.org/en-US/questions/1108691 and https://support.mozilla.org/en-US/questions/1108660 When I do an "email link" or click a "malto" in FF, if TB is already running, sometimes I get a mail compose window as I want, and sometimes I get the TB profile manager, which of course does not allow me to select the currently runnin TB profile, which is the one that I of course want. The only difference between the two scenarios is whether FF was started with the "-no-remote" option. I have established that TB is being started with the identical command line in both cases, so I am at a loss to understand why it behaves differently depending on how the FF that invokes it was started. How does TB decide whether it wants to invoke the profile manager when it is already running? For example, is there some registry value or ENV variable that FF or the OS might have set that it would look at other than the command line to start it? The exact same TB executable is being invoked also. Thanks.

Избрано решение

The problem is that FF sets the env variable MOZ_NO_REMOTE.

See https://support.mozilla.org/en-US/questions/1108691 solution for details.

Прочетете този отговор в контекста 👍 0

Всички отговори (1)

more options

Избрано решение

The problem is that FF sets the env variable MOZ_NO_REMOTE.

See https://support.mozilla.org/en-US/questions/1108691 solution for details.