-new-instance flag does not work
Categories
(Toolkit :: Startup and Profile System, defect, P5)
Tracking
()
People
(Reporter: fbrfa8.g, Unassigned)
References
Details
Comment 1•12 years ago
|
||
![]() |
||
Comment 2•12 years ago
|
||
Comment 4•12 years ago
|
||
Comment 6•12 years ago
|
||
Updated•12 years ago
|
Comment 8•11 years ago
|
||
Comment 9•11 years ago
|
||
Comment 10•11 years ago
|
||
Comment 11•11 years ago
|
||
Comment 13•11 years ago
|
||
Comment 14•11 years ago
|
||
Comment 15•11 years ago
|
||
Comment 16•10 years ago
|
||
Comment 17•8 years ago
|
||
Comment 18•8 years ago
|
||
Comment 19•8 years ago
|
||
Comment 20•8 years ago
|
||
Comment 21•7 years ago
|
||
Comment 22•7 years ago
|
||
Comment 23•7 years ago
|
||
Comment 24•7 years ago
|
||
Comment 25•7 years ago
|
||
Comment 27•7 years ago
|
||
Comment 28•7 years ago
|
||
Comment 29•6 years ago
|
||
Reporter | ||
Comment 30•6 years ago
|
||
Comment 31•6 years ago
|
||
Comment 32•6 years ago
|
||
Comment 33•6 years ago
|
||
Comment 34•6 years ago
|
||
Comment 35•6 years ago
|
||
Comment 37•6 years ago
|
||
In light of --new-instance
being desupported on Linux I'd assume that supporting it on Windows is WONTFIX, but that's a decision for the module owner.
Comment 38•6 years ago
|
||
Since bug 1518639 -new-instance now actually does something on Windows, but -no-remote and -new-instance are now largely pointless and may be removed at some point. See https://groups.google.com/forum/#!topic/mozilla.dev.platform/Vz-L_of5WZE
Comment 39•6 years ago
|
||
I agree with the resolution because I feel that the Container feature now covers this use case.
Comment 40•6 years ago
|
||
(In reply to Kriston from comment #39)
I agree with the resolution because I feel that the Container feature now covers this use case.
Considering that this bug is about opening new instances from a command line and being able to select the separate instance when opening links from sources OUTSIDE of firefox.
Considering the following bugs for the containers plugin I would say that the specified needs are NOT being met:
https://github.com/mozilla/multi-account-containers/issues/365
(Container cmdline option when opening URLs)
https://github.com/mozilla/multi-account-containers/issues/706
(Prompt about which container to use when opening link from external application)
https://github.com/mozilla/multi-account-containers/issues/1340
(First tab in each new session always opens in the default container)
Again: this use case is STILL not being addressed by firefox, SIX YEARS after the ticket was originally opened about this feature having BEEN BROKEN.
I used to work.
Then it didn't and it's been in limbo ever since despite a stupid number of people asking about it on a regular basis for the better part of a decade.
Comment 41•5 years ago
|
||
It used to work for me, i had this alias for throwaway profiles, for finance and other purpose.
alias fx="/Applications/Firefox.app/Contents/MacOS/firefox --new-instance --profile $(mktemp -d)"
I always used to find myself in safe-zone with this new profile, I use container tabs but explicit new profile folder used to make me feel bit safe. Hoping it get picked up.
Comment 42•5 years ago
|
||
(In reply to Sumit Murari from comment #41)
It used to work for me, i had this alias for throwaway profiles, for finance and other purpose.
alias fx="/Applications/Firefox.app/Contents/MacOS/firefox --new-instance --profile $(mktemp -d)"
I always used to find myself in safe-zone with this new profile, I use container tabs but explicit new profile folder used to make me feel bit safe. Hoping it get picked up.
New instance was without any add-ons, so that was also helpful.
I have just never been to chrome before or after much marketed quantum release. Still firefox make me go to chrome for incognito mode.
Comment 43•5 years ago
|
||
(In reply to Sumit Murari from comment #41)
It used to work for me, i had this alias for throwaway profiles, for finance and other purpose.
alias fx="/Applications/Firefox.app/Contents/MacOS/firefox --new-instance --profile $(mktemp -d)"
I always used to find myself in safe-zone with this new profile, I use container tabs but explicit new profile folder used to make me feel bit safe. Hoping it get picked up.
This issue only affects Microsoft Windows...
Comment 44•4 years ago
|
||
(In reply to Dave Townsend [:mossop] from comment #38)
Since bug 1518639 -new-instance now actually does something on Windows, but -no-remote and -new-instance are now largely pointless and may be removed at some point. See https://groups.google.com/forum/#!topic/mozilla.dev.platform/Vz-L_of5WZE
If I understand correctly, this bug has been resolved as "this feature is being abandoned and will not be made to work" - so the choice of `FIXED' for this seems rather confusing: if someone is trying to report a problem with the (still clearly documented) "--new-instance" flag not working, and they manage to come here (first result in Google), and the label says "FIXED" in 2018 - while the feature clearly does not work - it is very confusing.
I suggest to change the resolution to WONTFIX, and also removing these flags from the documentation, as they clearly aren't intended to ever work again.
Comment 45•4 years ago
|
||
(In reply to Oded Arbel from comment #44)
(In reply to Dave Townsend [:mossop] from comment #38)
Since bug 1518639 -new-instance now actually does something on Windows, but -no-remote and -new-instance are now largely pointless and may be removed at some point. See https://groups.google.com/forum/#!topic/mozilla.dev.platform/Vz-L_of5WZE
If I understand correctly, this bug has been resolved as "this feature is being abandoned and will not be made to work" - so the choice of `FIXED' for this seems rather confusing: if someone is trying to report a problem with the (still clearly documented) "--new-instance" flag not working, and they manage to come here (first result in Google), and the label says "FIXED" in 2018 - while the feature clearly does not work - it is very confusing.
To my recollection this is not correct. Bug 1518639 fixed -new-instance
to work on Windows as it does on other platforms, so what this bug was filed for is now fixed. However, like on all platforms, -new-instance
is not a terribly useful flag. Just passing an argument to select a profile that isn't in use will now give you a new Firefox instance whether this flag is present or not. All this flag does is alter the case when you launch Firefox with a profile that is already in use, without this flag Firefox will simply activate the existing Firefox instance using the profile, with this flag Firefox will refuse to start because the profile you are trying to use is in use and locked.
If you're seeing issues where -new-instance
is not behaving like this then please file a new bug and we can look at it.
Description
•