Actually (in 108) it appears to not be working at all.
The only reason (a) URL
might happen to open in a Private Window would be because you had focused on a Private Window prior to running the command line.
Had you not done that, had the last focused window being a non-Private Windows, the -private-window parameter would never open <URL> in a Private Window.
(I'm doing this using an existing session, so [other] Windows are already opened.)
So yeah, I'd say there is a bug in there.
---
In 102.4esr, -private-window <url> looks to work - in the singular case.
And it
appears that <url> is meant to be singular (i.e. not <url's>).
So you would need separate command lines to open multiple URLs in a Private Window.
- Code: Select all
firefox.exe -private-window www.google.com
firefox.exe -private-window slickdeals.net
firefox.exe -private-window forums.mozillazine.org
---
108 will open a (single) <url> in a Private Window - if FF is not already running.
If you pass it 2 url's, then 1 is opened in Private, then your (in my case) Session Restore session is opened, with the 2nd url opening in that restored session (in one of its' non-Private windows).
Again. (In 108) if FF is already open -private-window is ineffectual.
---
Again. (In 108) if FF is already open -private-window is ineffectual.
And lets not put that in stone - either.
(As it is, FF has become so incomprehensible, at this point, I am just left scratching my head.
I was going to file a bug, but because of the absurdity that is FF, I cannot "just" open a new, clean Profile & test.
So the best I can do is say something like, "there is a bug,
I think" - gross!)
---
Note,
https://bugzilla.mozilla.org/show_bug.cgi?id=1048286
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript