Consider usasge of the feature "remote"
The Firefox Remote Protocol is a low-level debugging interface based on the CDP protocol. With it, you can inspect the state and control execution of documents running in web content, instrument Gecko in interesting ways, simulate user interaction for automation purposes, and debug JavaScript execution
How it may be used in the mypal, if it is useless then to remove: delete the folder "remote" and references to it everywhere else.
AFAIK, Browser Toolbox (Ctrl-Alt-Shift-I) uses this protocol even for debugging it's own local Mypal.
Can you name any benefit of the protocol?
Perhaps, we are talking about different things, but:
Mypal's internal debugger presents in the "Web Developer" menu twice: on time as a debugger for web pages ("Developer Tools" Ctrl-Shift-I), and a second time as a debugger for browser itself ("Browser Toolbox" Ctrl-Alt-Shift-I).
When a user is starting the "Browser Toolbox", Mypal asks him:
And after successful connection debugger displays in its own window during a very short period of time:
As you see, debugger communicates with local debuggee (Mypal) via a network interface.
As far as I understand, removing the ability to communicate with remote targets will also kill the ability to debug Mypal itself and its add-ons.
Okey, I mean where practically this thing can be used. Why to use remote debugger on local?
Okey, I mean where practically this thing can be used.
Where? This is the only way to debug Mypal itself!
Press Ctrl-Alt-Shift-I, answer "Cancel" on an "Incoming Connection" window, and you will not get neither debugger, nor any other tool (Inspector, Console, Network Monitor, etc.)
Why to use remote debugger on local?
Let look at this issue from Mozilla developers POV: "Why to use two separate ways - one for local debugging, and another for remote one, if we can use the same for both?"
Moreover, Firefox is a multiplatform application, and IP-stack is the only common mechanism for inter-process communication across all supported operating systems.
This is the only way to debug Mypal itself
Really? What about older versions? And Seamonkey, does it have remote stuff?
Really? What about older versions? And Seamonkey, does it have remote stuff?
I suppose, this mechanism is even older then Firefox and Seamonkey, and existed in their predecessor - Mozilla Application Suite (if not Netscape Communicator).
And current versions of Seamonkey still use it.
Actually you confuse https://github.com/Feodor2/Mypal68/blob/main/remote/doc/Usage.md If the thing is present only in the nightly and disabled then we never use it. It was enabled on 1606604 So I ask about this particular feature
Actually you confuse
Indeed. As I wrote initially: "Perhaps, we are talking about different things".
https://github.com/Feodor2/Mypal68/blob/main/remote/doc/Usage.md
This description (or a feature itself) is confusing: it operates with a remote.enabled preference, and --remote-debugging-port <port> and --remote-debugger [<host>][:<port>] command line parameters.
But remote.* preferences branch consists of only remote.enabled, remote.force-local, and remote.log.level, whereas devtools.debugger.remote* family contains (among others) devtools.debugger.remote-enabled, devtools.debugger.remote-host, and devtools.debugger.remote-port, and these parameters are definitely related to the debugger I was talking about.
So I ask about this particular feature
If this is a really independent feature, then, most probably, nobody uses it. At least in Mypal. But you always can disable or delete it in the next release, and then look: will somebody complain or not?
Then the decision to delete "remote". Everybody welcome to do this. Anyway it probably become unusable after xul transfer, certainly impaired as I wont bother update it.
The mrionette another thing we can cosider it in the new topic.