Remove obsolete Firefox View prefs
Categories
(Firefox :: Firefox View, defect, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox125 | --- | wontfix |
| firefox126 | --- | wontfix |
| firefox127 | --- | fixed |
People
(Reporter: lagiann, Assigned: nsharpley)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [fidefe-firefox-view])
Attachments
(1 file)
Steps to reproduce:
Go to about:config and set any of the following options to "false" in Firefox 123
browser.tabs.firefox-view
browser.tabs.firefox-view-newIcon
browser.tabs.firefox-view-next
None of this options apparently works in Firefox 123.
In contrast, "browser.firefox-view.search.enabled" works as expected in 123 and all of them works normally in Firefox 122
Actual results:
Apparently nothing happens
Expected results:
Firefox should honor the option set.
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Firefox View' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•2 years ago
|
||
Those prefs were all supposed to be removed in various bugs as part of cleanup - they were intended for feature development only. It looks like they were accidentally added back into the profile.js file in bug 1783521 but they don't control anything anymore.
browser.firefox-view.search.enabled also is for feature development and will be removed.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 3•2 years ago
|
||
Since this is a task, I think it is ok to mark it's status as New, right?
Comment 4•2 years ago
|
||
(In reply to Monica Chiorean from comment #3)
Since this is a task, I think it is ok to mark it's status as New, right?
Yes, I've updated it.
| Assignee | ||
Comment 5•1 year ago
|
||
These were accidentally added back in to the profile.js file in bug 1783521 but don't do anything.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 7•1 year ago
|
||
| bugherder | ||
Comment 8•1 year ago
|
||
Set release status flags based on info from the regressing bug 1783521
Updated•1 year ago
|
Description
•