Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

-private-window Argument Not Working

  • 4 个回答
  • 1 人有此问题
  • 7 次查看
  • 最后回复者为 jonzn4SUSE

more options

macOS. Firefox is running. I enter: open -a Firefox --args -private-window "https://apple.com" (in Terminal or Automator) which I believe should open apple.com in a new private window, but although the focus change to the already open Firefox window, a new private window does not open. It does work (apple.com opens in a new private window) if Firefox is not already running, but I thought the -private-window argument is supposed to open a new private window whether Firefox is already running or not. What have I got wrong?

macOS. Firefox is running. I enter: open -a Firefox --args -private-window "https://apple.com" (in Terminal or Automator) which I believe should open apple.com in a new private window, but although the focus change to the already open Firefox window, a new private window does not open. It does work (apple.com opens in a new private window) if Firefox is not already running, but I thought the -private-window argument is supposed to open a new private window whether Firefox is already running or not. What have I got wrong?

所有回复 (4)

more options

Just woke up and had to read your issue again.  ;-) I cannot replicate the issue. see screenshot https://paste.opensuse.org/38002852

The upload finally worked. I made sure Firefox was not running and it worked.

由jonzn4SUSE于修改

more options

.....

由jonzn4SUSE于修改

more options

My problem is that is does not work when Firefox is ALREADY running, even though the description of the -private-window argument says "Opens a new private browsing window in an EXISTING instance of Firefox".

more options

I see the issue now, but is it a browser issue would be my question.