Sidebar would not remember last used panel
Categories
(Firefox :: Sidebar, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox-esr128 | --- | affected |
firefox131 | --- | wontfix |
firefox132 | --- | wontfix |
firefox133 | --- | fix-optional |
People
(Reporter: alice0775, Unassigned)
References
(Regression)
Details
(Keywords: nightly-community, regression, Whiteboard: [fidefe-sidebar])
Steps to reproduce:
- Open Firefox with new profile
- Put Sidebars toolbutton on Nav bar from Customize toolbar
- Click the Sidebars toolbutton
- Change sidebar panel from sidebar header to History from Bookmarks.
- Close the Sidebar
--- So, last used sidebar is History - Close the browser
- Re-open the browser with the same profile of step 1
- Click the Sidebars toolbutton
Actual results:
Sidebar opens Bookmarks panel
Expected results:
Sidebar should open last used panel. In this case History panel
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=26e8012d5da938871783505e3753b681ab8cb186&tochange=e86e777fced482506de767727a313be25003c673
Comment 1•1 month ago
|
||
:nsharpley, since you are the author of the regressor, bug 1885894, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Reporter | ||
Comment 3•1 month ago
|
||
(In reply to :Gijs (he/him) from comment #2)
I think this is a dupe of bug 1908019, right?
I do not think this is duplication.
Because, It reproduced with newly created profile and I am not using "Clear Recent History" and any related settings.
Comment 4•1 month ago
|
||
Not a duplication, but I think a bug 1908019 patch would solve it. I've picked that up from :sclements, so in progress.
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Reporter | ||
Comment 6•13 days ago
|
||
(In reply to Mathew Hodson from comment #5)
Was this fixed by bug 1908019?
I can still reproduce this on Nightly134.0a1(20241029155057) Windows11.
Comment 7•12 days ago
|
||
(In reply to Mathew Hodson from comment #5)
Was this fixed by bug 1908019?
No, that bug was for a different issue altogether.
Updated•8 days ago
|
Description
•