Closed Bug 1798748 Opened 1 year ago Closed 1 year ago

duplicated entries in the command-line --help output

Categories

(Core :: Widget: Gtk, enhancement, P3)

Firefox 106
enhancement

Tracking

()

RESOLVED FIXED
111 Branch
Tracking Status
firefox111 --- fixed

People

(Reporter: patrice.duroux, Assigned: milos.milovanovic)

Details

(Keywords: good-first-bug)

Attachments

(1 file, 3 obsolete files)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:106.0) Gecko/20100101 Firefox/106.0

Steps to reproduce:

OS: Debian GNU/Linux bookworm/sid
Arch: amd64
Package version: 106.0-1

$ firefox --help

Actual results:

I am getting:

Usage: firefox [ options ... ] [URL]
where options include:

X11 options
--display=DISPLAY X display to use
--sync Make X calls synchronous
--g-fatal-warnings Make all warnings fatal

Firefox options
-h or --help Print this message.
-v or --version Print Firefox version.
--full-version Print Firefox version, build and platform build ids.
-P <profile> Start with <profile>.
--profile <path> Start with profile at <path>.
--migration Start with migration wizard.
--ProfileManager Start with ProfileManager.
--no-remote Do not accept or send remote commands; implies
--new-instance.
--new-instance Open new instance, not a new window in running instance.
--safe-mode Disables extensions and themes for this session.
--allow-downgrade Allows downgrading a profile.
--MOZ_LOG=<modules> Treated as MOZ_LOG=<modules> environment variable,
overrides it.
--MOZ_LOG_FILE=<file> Treated as MOZ_LOG_FILE=<file> environment variable,
overrides it. If MOZ_LOG_FILE is not specified as an
argument or as an environment variable, logging will be
written to stdout.
--headless Run without a GUI.
--jsdebugger [<path>] Open the Browser Toolbox. Defaults to the local build
but can be overridden by a firefox path.
--wait-for-jsdebugger Spin event loop until JS debugger connects.
Enables debugging (some) application startup code paths.
Only has an effect when --jsdebugger is also supplied.
--start-debugger-server [ws:][ <port> | <path> ] Start the devtools server on
a TCP port or Unix domain socket path. Defaults to TCP port
6000. Use WebSocket protocol if ws: prefix is specified.
--browser Open a browser window.
--new-window <url> Open <url> in a new window.
--new-tab <url> Open <url> in a new tab.
--private-window <url> Open <url> in a new private window.
--preferences Open Preferences dialog.
--screenshot [<path>] Save screenshot to <path> or in working directory.
--window-size width[,height] Width and optionally height of screenshot.
--search <term> Search <term> with your default search engine.
--setDefaultBrowser Set this app as the default browser.
--first-startup Run post-install actions before opening a new window.
--kiosk Start the browser in kiosk mode.
--disable-pinch Disable touch-screen and touch-pad pinch gestures.
--jsconsole Open the Browser Console.
--jsdebugger [<path>] Open the Browser Toolbox. Defaults to the local build
but can be overridden by a firefox path.
--wait-for-jsdebugger Spin event loop until JS debugger connects.
Enables debugging (some) application startup code paths.
Only has an effect when --jsdebugger is also supplied.
--devtools Open DevTools on initial load.
--start-debugger-server [ws:][ <port> | <path> ] Start the devtools server on
a TCP port or Unix domain socket path. Defaults to TCP port
6000. Use WebSocket protocol if ws: prefix is specified.
--marionette Enable remote control server.
--remote-debugging-port [<port>] Start the Firefox Remote Agent,
which is a low-level remote debugging interface used for WebDriver
BiDi and CDP. Defaults to port 9222.
--remote-allow-hosts <hosts> Values of the Host header to allow for incoming requests.
Please read security guidelines at https://firefox-source-docs.mozilla.org/remote/Security.html
--remote-allow-origins <origins> Values of the Origin header to allow for incoming requests.
Please read security guidelines at https://firefox-source-docs.mozilla.org/remote/Security.html

Expected results:

No duplications regarding the options --jsdebugger, --start-debugger-server, and --wait-for-jsdebugger

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core
Keywords: good-first-bug
Priority: -- → P3

Hey folks, I'm new to Mozilla community and I would like to work on this bug as my first bug. Is there anyone else working on this bug already? If not, are you ok that I start working on this one?
Thanks!
Milos

Assignee: nobody → milos.milovanovic
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Attachment #9307870 - Attachment description: WIP: Bug 1798748 - Fix for command line help output to include arguments --jsdebugger, --wait-for-jsdebugger and --start-debugger-server only once → Bug 1798748 - Fix for command line help output to include arguments --jsdebugger, --wait-for-jsdebugger and --start-debugger-server only once
Attachment #9307870 - Attachment is obsolete: true
Attachment #9308552 - Attachment is obsolete: true
Attachment #9309215 - Attachment is obsolete: true
Pushed by nalexander@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c6c2f65ec724
Fix for command line help output to include arguments --jsdebugger, --wait-for-jsdebugger and --start-debugger-server only once r=nalexander
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch
You need to log in before you can comment on or make changes to this bug.