Closed
Bug 1499395
Opened 6 years ago
Closed 6 years ago
Custom Profile Name is overwritten by dedicated profiles logic
Categories
(Toolkit :: Startup and Profile System, defect)
Toolkit
Startup and Profile System
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox62 | --- | unaffected |
firefox63 | --- | unaffected |
firefox64 | --- | unaffected |
People
(Reporter: aflorinescu, Assigned: mossop)
References
Details
[Environment:]
Windows 8.1 / Mac Osx 10.13
[Steps:]
See STR. from https://bugzilla.mozilla.org/show_bug.cgi?id=1499388#c0
[Actual Result:]
When taken over by dedicated logic, Custom Profile Name is overwritten.
[Profile1]
Name=default-2656FF1E876E9973
IsRelative=1
Path=Profiles/49v8sw31.zzzz
[Expected Result:]
Taken in consideration that there was a discussion about making the dedicated profile names more user friendly, I think the first step would be fixing this issue, which means that we should use the existent profile name + the installation hash.
e.g.: for the above example, the dedicated profile should look:
[Profile1]
Name=zzzz-2656FF1E876E9973
IsRelative=1
Path=Profiles/49v8sw31.zzzz
I'm not very confident about this, but I would also have the channel added to this naming logic. It's kinda'of backwards, but in this way, we would align profile naming logic to dev-edition.
So for the above example, we'd have something like:
[Profile1]
Name=zzzz-2656FF1E876E9973-beta
IsRelative=1
Path=Profiles/49v8sw31.zzzz
Assignee | ||
Comment 1•6 years ago
|
||
I can update the logic so it only renames the profile if it is currently named "Default" (or "dev-edition-default" on dev-edition).
Assignee: nobody → dtownsend
Assignee | ||
Comment 2•6 years ago
|
||
This is fixed locally.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•