1179743 - [PATCH] Profile (P) command line argument passed to remote

Status: UNCONFIRMED

Description

[Matthew W.S. Bell]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Iceweasel/38.0.1
Build ID: 20150526223604

Steps to reproduce:

Start an instance of Firefox.
From the command line, run "firefox -P <profile>", where <profile> is different from the profile in the above instance.


Actual results:

A new window in the initial Firefox instance opens.


Expected results:

A new instance of Firefox with the specified profile should open.

Comment 1

[Matthew W.S. Bell]

Created attachment 8628780 [details] [diff] [review]
nsAppRunner: CheckArg() operate without removing argument

Comment 2

[Matthew W.S. Bell]

Created attachment 8628782 [details] [diff] [review]
nsAppRunner: Process profile in RemoteCommandLine().patch

Comment 3

[Matthew W.S. Bell]

bug 1167869 may be related.

Comment 4

[Benjamin Smedberg]

XULRunner has been removed from the Mozilla tree: see https://groups.google.com/forum/#!topic/mozilla.dev.platform/_rFMunG2Bgw for context.

I am closing all the bugs currently in the XULRunner bugzilla component, in preparation for moving this component to the graveyard. If this bug is still valid in a XULRunner-less world, it will need to be moved to a different bugzilla component to be reopened.

Comment 5

[Matthew W.S. Bell]

Reopening and reassigning on the basis that the file toolkit/xre/nsAppRunner.cpp is still present in Firefox 53, and I am still experiencing the bug on the same. I believe the product and component to be correct, but I don't seem to be able to find a canonical definition anywhere.

Comment 6

[Matthew W.S. Bell]

Make that in Firefox 52

Comment 7

[Benjamin Smedberg]

As with many similar bugs, I'm not sure we should fix this. The complexity of actually getting this right is high, and -profile is primarily for testing purposes where -no-remote is fine.

Comment 8

[Matthew W.S. Bell]

I know of at least some use in anger.

Do you propose providing an error message and exiting in situations that are known not to work then?