Removing the -no-remote command line argument

361 views
Skip to first unread message

Dave Townsend

unread,
Jul 4, 2024, 6:01:27 AM7/4/24
to dev-pl...@mozilla.org
See bug 1906260[1] for more details but I am planning on removing the -no-remote command line argument from Firefox. This has been unneeded since Firefox 67 when we started supporting running multiple profiles simultaneously without it. The only effect right now is often to cause some user confusion as many tools and websites recommend its use. In the future its use will break some new functionality we are adding with the new profiles work. We will retain the -new-instance argument which bypasses the startup check for other running instances using the same profile which is essentially the same thing (though you pass this argument on subsequent instances rather than the first instance).

Please let me know if you know of any reason not to remove this.

Dave Townsend

unread,
Jul 4, 2024, 6:36:41 AM7/4/24
to dev-pl...@mozilla.org
Note that I am also planning on removing support for the MOZ_NO_REMOTE environment variable which is an alternative way of doing the same thing as the -no-remote command line argument.

Nick Alexander

unread,
Jul 4, 2024, 2:37:48 PM7/4/24
to Dave Townsend, dev-pl...@mozilla.org
Dave,

On Thu, Jul 4, 2024 at 3:01 AM 'Dave Townsend' via dev-pl...@mozilla.org <dev-pl...@mozilla.org> wrote:
See bug 1906260[1] for more details but I am planning on removing the -no-remote command line argument from Firefox. This has been unneeded since Firefox 67 when we started supporting running multiple profiles simultaneously without it. The only effect right now is often to cause some user confusion as many tools and websites recommend its use. In the future its use will break some new functionality we are adding with the new profiles work. We will retain the -new-instance argument which bypasses the startup check for other running instances using the same profile which is essentially the same thing (though you pass this argument on subsequent instances rather than the first instance).

Please let me know if you know of any reason not to remove this.

I agree, we should remove `-no-remote`!  In addition to all of the reasons given here, the remoting protocol is used to deliver Windows native notifications correctly and disabling it will cause bad interactions with that system.

Thanks for doing this!
Nick
Reply all
Reply to author
Forward
0 new messages