Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Can't open new tabs in Firefox from the command line on a Mac

  • 2 respostas
  • 1 tem este problema
  • 6 visualizações
  • Última resposta de cor-el

more options

If I run

   /Applications/Firefox.app/Contents/MacOS/firefox -new-tab https://www.mozilla.org

when Firefox is already running, I get the error "A copy of Firefox is already open. Only one copy of Firefox can be open at a time." It is true that Firefox is already running, but what I am shooting for is getting a new tab in the already running instance, as the -new-tab flag indicates. I get this problem even if the already running instance was started with exactly the same command.

Some of the flags at https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options explicitly say they open new tabs or windows within an existing instance of Firefox, such as -private-window, but I get the same behavior with those flags. What am I doing wrong?

If I run /Applications/Firefox.app/Contents/MacOS/firefox -new-tab https://www.mozilla.org when Firefox is already running, I get the error "A copy of Firefox is already open. Only one copy of Firefox can be open at a time." It is true that Firefox is already running, but what I am shooting for is getting a new tab in the already running instance, as the -new-tab flag indicates. I get this problem even if the already running instance was started with exactly the same command. Some of the flags at https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options explicitly say they open new tabs or windows within an existing instance of Firefox, such as -private-window, but I get the same behavior with those flags. What am I doing wrong?

Todas as respostas (2)

more options

It appears that as of five years ago this was a known bug with no intended fix: https://bugzilla.mozilla.org/show_bug.cgi?id=393645

more options