1844938 - "Restart Firefox" after enabling "Always use private browsing mode" leads to incorrect URL opening.

Status: RESOLVED INCOMPLETE

(Firefox :: Settings UI, defect)

Description

[bugcatcher66]

Attachment: "Restart Firefox" after enabling "Always use private browsing mode" leads to incorrect URL opening.

[Affected Versions]

• Firefox 115.0.2 (64-bit)

[Affected Platforms]

• windows 10 x64

[Steps to reproduce]:

1. Go to "about:preferences#privacy".
2. Select "Use custom settings for history" from the "History" section.
3. Select the "Always use private browsing mode" option.
4. Click the "Restart Firefox" button in the pop-up.

[Expected result]:

• After step 4, Firefox restarts and open with its default start page.

[Actual result]:

• After step 4, Firefox restarts, but instead of the default start page, it opens a configuration page with the following URL: chrome://browser/locale/browser.properties

[Notes]:
-Not all devices may experience this issue, but if it occurs, any restart method triggers the problem.

Comment 1

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

Hello,

Thanks for filing this bug.

Would you be willing to help us narrow down when this bug was introduced, using the mozregression tool? See the docs at http://mozilla.github.io/mozregression/ for guidance. Thank you!

Comment 2

[Mike Conley (:mconley) (:⚙️)]

Hi bugcatcher66,

We're also curious to know if you can reproduce this issue with a new profile.

Comment 3

[Monica Chiorean]

I am not able to reproduce the issue on Winx64 using FF build 115.0.2(20230710165010) and steps from description, after restart I get the home page.
Are there any other steps that we need to follow? Also does the issue reproduce with new profile? (https://support.mozilla.org/en-US/kb/troubleshoot-and-diagnose-firefox-problems#w_6-create-a-new-firefox-profile)
Thank you.

Comment 4

[Mike Conley (:mconley) (:⚙️)]

We haven't heard from the reporter in about a month, so closing this as INCOMPLETE.

bugcatcher66 - if you are able to provide the information in comment 1 and / or comment 2, we can re-open this bug and try to sort out what's going on.