You might want to file an upstream bug at
https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox to request
the old behaviour back, or at least ask for a console warning when using
the "-private" flag together with a URL, or when there's already a
running instance.
If you do please link it h
Sorry for the delay.
I see what you mean, it seems true that firefox (suddenly?) adheres to
the documentation (and hasn't done so in the past?).
So in future we have to keep in mind that
$firefox -private
does not open a private window (anymore!) if another instance of firefox is
already runni
Sorry ts, I had misunderstood the problem you described.
I can confirm that with no previously running instance of firefox,
executing "firefox -private URL" opens the URL but *not* in a private
window. However running the same command without a URL parameter does
open a private window as expected.
Thanks Olivier, for the additional reference to the documentation.
This, however, is not the described problem.
The observed bug is that calling firefox from bash with the option
"-private" does open firefox, but not in private mode.
Thanks for your understanding.
--
You received this bug noti
Fwiw, I don't see how this would be a support request or spam ("changed
to invalid"), it looks like a bug in the sense of a piece of software
not performing as advertised, to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
According to the upstream documentation
(https://developer.mozilla.org/fr/docs/Mozilla/Command_Line_Options#-private),
"-private" is to initially open firefox in private browsing mode,
whereas "-private-window URL" is to open the URL in a new private window
when a firefox instance is already runnin
