Dedicated profiles don't get locked to the default browser install

RESOLVED FIXED in Firefox 67

Status

()

enhancement
RESOLVED FIXED
4 months ago
2 months ago

People

(Reporter: mossop, Assigned: mossop)

Tracking

unspecified
mozilla67
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox67 fixed)

Details

Attachments

(1 attachment)

When choosing the old default profile as the new dedicated profile when the app is the default browser we're meant to "lock" the profile to this install so others won't choose it later. Not sure how I failed to catch this in tests but this doesn't work because we try to get an XPCOM component before XPCOM is started.

Assignee

Updated

4 months ago
Assignee: nobody → dtownsend
Assignee

Comment 1

4 months ago

Previously we attempted to do this when XPCOM wasn't available so it always
failed to get the shell service. Instead set a flag telling us to do it later
when we choose the old default profile.

Also includes a block of code to attempt to fix the issue for existing nightly
users, this can be removed before betas.

Comment 2

4 months ago
Pushed by dtownsend@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c132ef1b7c8a
Check if this is the default install and if so lock the profile. r=froydnj

Comment 3

4 months ago
bugherder
Status: NEW → RESOLVED
Last Resolved: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
Assignee

Updated

2 months ago
Blocks: 1535367
You need to log in before you can comment on or make changes to this bug.