Make -new-instance do what it used to.
Categories
(Toolkit :: Startup and Profile System, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox67 | --- | fixed |
People
(Reporter: mossop, Assigned: mossop)
References
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
I made a mistake in thinking that -no-remote and -new-instance did the same thing. In fact -no-remote disables the remote system entirely but -new-instance only disable the client part. Folks have suggested that is still useful so this makes it do what it used to.
|
Assignee | |
Comment 1•6 years ago
|
||
|
||
Comment 3•6 years ago
|
||
Thanks for doing this; from the original description of the profile changes it sounded as if this might not be feasible to fix.
Historical context, for reference: Originally -no-remote meant only “no remote client”, and then it was changed to “no remote client or server” in bug 650078, which broke people who were using the old meaning (e.g., me), so -new-instance was added in bug 716110… but only on Unix/X11, because the then-volunteer who showed up with a patch (i.e., me) didn't have access to Windows or know how the remote commands worked there. And then bug 855899, for -new-instance on Windows, never found anyone to work on it.
|
||
Comment 4•6 years ago
|
||
| bugherder | ||
Description
•