You can no longer rely on "documentation" or even your own pre-existing knowledge to know what to do - because FF 67 change what & how things work.
And even better then that, they are rather lax at 1) telling us that anything changed (in any meaningful way) 2) seem not to even want to document just what changed & how one is supposed to work (now) in situations that has always worked (up to now). Openness!
@willi, on the Portable end, is that also a FF 67 Portable version? And you are running FirefoxPortable.exe rather then firefox.exe (directly)?
if you are aware of command line parameters there is no need for portableapps
Command line options no longer work as they once did. See above.
in any other case you need to start firefox with a parameter for profile (using profiles.ini) or path (portableapps) to start another tab/window
And just
how do you do that?
fail: firefox -p profile2 -url
www.google.com
fail: firefox -p profile2 -url
www.google.com -no-remote
the multi-account container extension
Whatever that might be, or even if it is build into FF, it is still different from running more then one
instance.
(And also, in the past, one understood what that entailed, & how it worked, & what to expect. That is not longer the case with 67.)
1. ridiculous
2. ridiculous
3. ridiculous (basically). I wouldn't know about pinning & yes, you should always (only) use Firefoxportable.exe.
If FF Portable is 67, no telling what might happen [see above].
With FF 67, no telling what might happen?
You now have to have a mighty clear understanding of just how FF 67 now works - which we don't [see above].
Fore instance, if FF 67, when it goes to start up, checks for an already existing process named, "firefox.exe", then alters its behavior based on that...
If something like that is the case, then well golly gee, starting a "regular" instance of FF 67 will see already running instance of "firefox.exe" that was spawned by the portable-apps launcher, Firefoxportable.exe. And how or if that changes things, well we just don't know [see above].
If you start FF first, or if you start Portable first, or ... who knows?
Portable has always been self-contained.
It did not rely on profiles.ini (or this new installs.ini - whatever that is).
Changes to profile.ini or changes to FF outside of Portable, never had any affect on the Portable version.
Does it now ... who knows?
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