Can we remove old command line parameters?
florian at queze.net
Thu Mar 29 13:03:19 UTC 2018
I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1449922 to
investigate removing old command line parameters that I suspect of
Added in toolkit for Fennec's Debian packaging in bug 469076 9 years ago.
Added in browser/ in bug 324023 12 years ago. Meant to be used along
with -setDefaultBrowser. I doubt this is used.
I doubt this is still useful now that add-ons can't register chrome
We could keep the "chrome://browser/content/pref/pref.xul" and
"chrome://browser/content/preferences/preferences.xul" special case
that opens the preferences. This was added 13 years ago in bug 285416.
I don't know how likely users are to still have shortcuts pointing to
this in their start menu. It's probably pretty rare at this point.
Added in bug 375710 11 years ago as "debugging code" (bug 375710
comment 75). Doesn't seem to have been used since that.
We could maybe even remove toolkit/components/nsDefaultCLH.js
entirely. It provides the above two -print-xpcom-dir* parameters, the
-silent parameter, toolkit.singletonWindowType (the last consumer of
this was Instantbird), toolkit.defaultChromeURI (which has some
references in m-c, but none of them in Firefox Desktop).
Like all command line handlers, this component is loaded during
startup, and for apparently very little value for Firefox users.
Any opinion or objection?
More information about the firefox-dev