Open Bug 1999047 Opened 9 months ago Updated 9 days ago

the --private-window command line parameter does not work when an empty string is supplied

Categories

(Firefox :: Private Browsing, defect, P3)

defect

Tracking

()

ASSIGNED

People

(Reporter: jogihoogi, Assigned: mraiber)

References

(Depends on 1 open bug)

Details

Steps to reproduce:

  1. install firefox (my version is 128.14.0esr on debian 13)
  2. firefox --private-window ''
    in regards to 2. any empty string will lead to the same behaviour

Actual results:

it opens a new window that isnt in private mode

Expected results:

it should open a window that is in private mode

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

Component: Untriaged → Private Browsing

Hello, thank you for the bug report!

Unfortunately I could not reproduce your issue, as a private window is opened every time I use the command line. Would you be so kind as to answer a few questions so we can investigate this further?

  • Are there any other configurations needed to be set in order to reproduce this issue?
  • Is the private window opened correctly if opening a website with the command?

Thank you.

Flags: needinfo?(jogihoogi)

no other configurations here is a screenshot of how i can reliably reproduce it:
it also doesn't matter if single ' or double " quotes are used as in '' or "" when the string is empty it opens a non private browsing video
and it works normally when a url is supplied as in 'firefox --private-window google.com' for example.

Flags: needinfo?(jogihoogi)

sorry... it ate the image url

The severity field is not set for this bug.
:timhuang, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(tihuang)
Severity: -- → S3
Flags: needinfo?(tihuang)
Priority: -- → P3
Assignee: nobody → mraiber
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Depends on: 1733835
You need to log in before you can comment on or make changes to this bug.