Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

-private-window Argument Not Working

  • 4 Antworten
  • 1 hat dieses Problem
  • 2 Aufrufe
  • Letzte Antwort von 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?

Alle Antworten (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.

Geändert am von jonzn4SUSE

more options

.....

Geändert am von 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.