Make -new-instance do what it used to.

RESOLVED FIXED in Firefox 67

Status

()

enhancement
RESOLVED FIXED
2 months ago
2 months ago

People

(Reporter: mossop, Assigned: mossop)

Tracking

unspecified
mozilla67
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox67 fixed)

Details

Attachments

(1 attachment)

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.

Comment 2

2 months ago
Pushed by dtownsend@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/767ee8714acf
Make -new-instance only stop searching for existing instances on startup. r=jmathies
Assignee

Updated

2 months ago
Blocks: 1518639

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

2 months ago
bugherder
Status: NEW → RESOLVED
Last Resolved: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in before you can comment on or make changes to this bug.