There's a bit of an edge case where the profile manager is shown unexpectedly and different from previous behaviour, but this may be difficult to avoid. It happens when a
-no-remote instance/profile is opened after a remote one, and becomes the last-selected.
(on Windows, Firefox 67.0.4)
- Configure Firefox to show profile manager (untick "use selected without asking")
- Start an instance of Firefox normally, using
- Start an instance of Firefox with
- Open a URL with system default handler, e.g.
start http://google.com in Windows cmd
- Profile manager shows up, with the
default is selected now, the URL opens in the existing instance and future invocations correctly select the last-selected
default and open in the existing instance automatically
Previously, this would have defaulted to the one "remote" instance available. Now, it tries for the "last selected" profile, even if that's a
One possible way around it that I can see is to maintain a separate "last selected" and "last remote" profile. "last selected" being what is displayed in the profile manager on next launch, including
-no-remotes as it currently is, but the profile tried for remoting should not be updated when a new
-no-remote instance is launched, i.e. it should only try the last remoting-enabled instance/profile. Perhaps add a new field to
DefaultRemote in addition to
It's not a huge issue, and may not be worth the effort to fix, but I'll mention it here because it confused me the first few times I encountered it.