Closed
Bug 111474
Opened 23 years ago
Closed 23 years ago
selected order of sidebar tabs not persistant
Categories
(SeaMonkey :: Sidebar, defect)
Tracking
(Not tracked)
People
(Reporter: m_mozilla, Assigned: samir_bugzilla)
References
()
Details
I just downloaded 0.9.6 for MacOSX and then added a bunch of sidebar tabs to see what they were. I deleted most of them, and then re-ordered the remaining tabs. At that time, my specified order (call it "order A") was what I saw in the sidebar. I exited Mozilla and re-launched. The tabs were now in a different order (call it "order B"). My previously-selected tab was still displayed... but it wasn't at the top of the list of tabs anymore. I exited Mozilla and re-launched. The tabs were still in "order B" rather than the "order A" I had specified. I opened the customize sidebar dialog and saw that *it* showed my sidebars in "order A" even though the browser was rendering them in "order B". I exited Mozilla and re-launched. The tabs were now in "order C": a new ordering which was not the order I had specified and was not the previous incorrect ordering. I hid the sidebar. I unhid it. It was still in "order C". I opened a new window. The new window had tabs in "order A", the order I had specified. I used the new window to search for the bug to see if it had been reported. I didn't find it, and so used this window to report the bug. The URL provided above is to a screenshot showing two windows. The left window in the background in the new window which has the tabs in the correct "order A" order. The foreground window on the right is the window into which I'm typing this bug, which has the tabs in the incorrect "order C" order. Note that the correct order of the last three tabs is CSS, HTML, CNN. The HTML, CNN, CSS order is not what I specified in the dialog box. -matt
*** This bug has been marked as a duplicate of 55358 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•