Sidebar launcher and panel appear in the incorrect order sometimes on restart
Categories
(Firefox :: Sidebar, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox131 | --- | fixed |
People
(Reporter: nsharpley, Assigned: nsharpley)
References
Details
(Whiteboard: [fidefe-sidebar])
Attachments
(2 files)
See screenshot. There was a recent change moving setPosition
to init
in browser-sidebar.js
, uncovering the need for removing order
from SessionStore
data to avoid conflict.
Assignee | ||
Comment 1•8 months ago
|
||
We can rely on the global pref for this. setPosition
in browswer-sidebar.js
looks
at the pref sidebar-position_start
to determine "order" on init
and on reversePosition
Updated•8 months ago
|
Assignee | ||
Updated•8 months ago
|
Updated•8 months ago
|
Comment 4•4 months ago
|
||
I would like to attempt this bug's fix verification. Could you please provide us with some steps to reproduce? Thank you.
Assignee | ||
Comment 5•4 months ago
|
||
:danibodea, no worries!
STR:
- Open a window and set the
sidebar.revamp
pref to true in Firefox Labs - Open any panel (eg. Customize Sidebar)
- Quit Firefox.
- Restart the browser and restore the session.
Expected - The sidebar panel should be open and the order of the elements should be sidebar-main
, sidebar-splitter
, sidebar-box
(opposite for RTL or sidebar.position_start = false
)
Actual - The sidebar-box
was before the sidebar-main
and sidebar-splitter
elements.
Comment 6•4 months ago
|
||
I can't seem to be able to reproduce your issue on MacOS11 or MacOS14 ARM with Nigyhtly v131.0a1 from 2024-08-26. The provided steps to reproduce are not valid and verification is not possible.
I've tried creating random history and data to simulate a "normal account" and also tried them on fresh user profiles, but the UI issue was not observed.
Do you think you can provide an improved set of steps to reproduce?
Do you know whether this issue could be specific to a device or an operating system?
Which MacOS version have you observed it on?
Thanks!
Assignee | ||
Comment 7•4 months ago
|
||
This was from four months ago so I am not sure what MacOS version I was on. I'm sorry I can't provide any further STR - it was a random occurrence at start up. I observed it on a local build. Thanks!
Comment 8•3 months ago
|
||
Removing qe-verify+ tag since STR cannot be provided. Verification can not be provided.
Description
•