Support using the remoting service to send command lines after startup
Categories
(Toolkit :: Startup and Profile System, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox131 | --- | fixed |
People
(Reporter: mossop, Assigned: mossop)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fidefe-profile-management] )
Attachments
(6 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
Bug 1892400: Remove the startup token from the non-unix remote implementations. r=jhirsch!,glandium!
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
Currently we can only send a command line to a running Firefox in a specific point during early startup. There is nothing stopping us making this available more generally to allow sending messages to other instances at any point during the application lifecycle.
Updated•5 months ago
|
Assignee | ||
Comment 1•5 months ago
|
||
Assignee | ||
Comment 2•5 months ago
|
||
Assignee | ||
Comment 3•5 months ago
|
||
Updated•5 months ago
|
Assignee | ||
Comment 4•3 months ago
|
||
Currently the windows client sends the current process command line which is
potentially an issue since some of those arguments may have been consumed
already. It will also not support sending custom command lines after startup.
Assignee | ||
Comment 5•3 months ago
|
||
This simplifies the call signatures of all versions since this is only needed in unix.
Assignee | ||
Comment 6•3 months ago
|
||
With the new profiles implementation we need to be able to identify a running instance
regardless of whether it was launched as a named profile or not. This changes to prefer
using the full profile path as an identifier falling back to testing the profile name
for backwards compatibility.
Assignee | ||
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Updated•2 months ago
|
Comment 7•2 months ago
|
||
Currently we can only send a command line to a running Firefox in a specific point during early startup.
I'm not sure what you mean here. If I firefox --jsconsole
while firefox is running, that opens the jsconsole in the running firefox.
Assignee | ||
Comment 8•2 months ago
|
||
(In reply to Mike Hommey [:glandium] from comment #7)
Currently we can only send a command line to a running Firefox in a specific point during early startup.
I'm not sure what you mean here. If I
firefox --jsconsole
while firefox is running, that opens the jsconsole in the running firefox.
I mean from a Firefox process. We can launch a new Firefox process yes but that is unneeded overhead.
Comment 9•2 months ago
|
||
I see what you mean now. Thank you for the clarification.
Comment 10•2 months ago
|
||
Depends on bug 1906260 because https://phabricator.services.mozilla.com/D217569 is part of the patch stack.
Comment 11•2 months ago
|
||
Comment 12•2 months ago
|
||
Backed out for causing Gtest failures
Backout link: https://hg.mozilla.org/integration/autoland/rev/3c69f0b52085ffe6c4619391f19c0f9cf41244d2
Comment 13•1 month ago
|
||
Comment 14•1 month ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/8bc2789652db
https://hg.mozilla.org/mozilla-central/rev/c62cf2fcd7a1
https://hg.mozilla.org/mozilla-central/rev/56ee67701929
https://hg.mozilla.org/mozilla-central/rev/ab78fe7e1029
https://hg.mozilla.org/mozilla-central/rev/dab3567a33f3
https://hg.mozilla.org/mozilla-central/rev/259fd33ad3af
Assignee | ||
Updated•26 days ago
|
Description
•