Can not create selectable profiles as the option is not available in the hamburger menu.
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr140 | --- | unaffected |
| firefox-esr153 | --- | unaffected |
| firefox152 | --- | unaffected |
| firefox153 | --- | unaffected |
| firefox154 | --- | fixed |
People
(Reporter: mchiorean, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
|
227.06 KB,
image/png
|
Details |
Found in
- version: 154.0a1(20260708220003)
Affected versions
- versions: 154.0a1
Tested platforms
- Affected platforms: Windows, Ubuntu, Mac
- Unaffected platforms: -
Steps to reproduce
- Have the latest nightly build installed with a clean profile.
- Check that user is able to add a selectable profile from Hamburger menu.
Expected result
- Add profile option should be available on Hamburger menu(check screenshot attached).
Actual result
- Option is missing on latest Nightly build 154.0a1(20260708220003).
Regression range
- Issue does not seem to reproduce on earlier nightly build 154.0a1(20260702212026) and neither on Beta 153.0b10 nor on release 152.0.5.
- Could not check with mozregression as option(Add profiles) is not available on any build.
Notes
- Pref 'browser.profiles.enabled' is enabled by default, so it is not a pref issue.
- Also if component is not correct please update.
| Reporter | ||
Updated•1 month ago
|
| Reporter | ||
Updated•1 month ago
|
Comment 1•1 month ago
|
||
This appears to be a regression. I manually narrowed down the regression range, and the resulting pushlog is:
I suspect Bug 2007074 may be the culprit. Please let me know if you'd like me to investigate this further.
Comment 2•1 month ago
|
||
Simona, I suspect bug 2046787 is the culprit. I'm currently working on bug 2046848 which should resolve this issue.
Updated•1 month ago
|
Comment 3•1 month ago
|
||
(In reply to Nikki Sharpley (:nikkis) (she/her) from comment #2)
Simona, I suspect bug 2046787 is the culprit. I'm currently working on bug 2046848 which should resolve this issue.
Thank you, Nikki! I was thinking Bug 2046787 was the regressor as well. I'm not sure how I managed to copy the wrong bug number, though.
Comment 4•1 month ago
|
||
Set release status flags based on info from the regressing bug 2046787
Updated•1 month ago
|
Updated•1 month ago
|
Comment 5•1 month ago
|
||
Set release status flags based on info from the regressing bug 2046787
Updated•1 month ago
|
Description
•