Closed Bug 34728 Opened 25 years ago Closed 25 years ago

Closed state does not persist for Sidebar

Categories

(SeaMonkey :: Sidebar, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: cmaximus, Assigned: slamm)

References

Details

(Whiteboard: [nsbeta2+])

***Overview Description: If you click the slider to close the sidebar and quit the browser, the closed state does not persist when you relaunch the browser. ***Steps to Reproduce: 1) Click the slider to close the Sidebar. 2) Quit the browser. 3) Launch Seamonkey. ***Actual Results: Your sidebar is open again. ***Expected Results: Your sidebar should remain closed, more generally it should maintain whatever state it was left in. ***Build Date & Platform Bug Info: reproduced on WinNT 2000040509 and MacOS 2000040510. DOES NOT occur on Linux 2000040509.
cc:ing waterson since slamm is out of town
spam: changing qa contact on sidebar bugs from paulmac to shrir@netscape.com (all 67 of them!)
QA Contact: paulmac → shrir
I was hoping someone more knowledgable could sort this out but thes bugs look like dupes of each other. The confusing thing is some have different components Some are in diffrent components also. bug 34728 bug 35093 bug 35654 and part of bug 35757 related to bouncing. I will let someone else pick what bug to mark the other a dupe of.
Thanks for looking at these! I doubt I'm "someone more knowledgable" but here goes anyways: bug #34728 is definitely not the same as this bug. [It is concerned with persisting the open/closed state of the sidebar between browser sessions]. However, I basically agree that bug #35093, bug #35654, and bug #35757 are all facets of the same broken behaviour (in order, 'first noticed', 'won't close', 'won't close and blanks content'). I'm marking bug #35654 as a dup of bug #35093 but I'll let evaughan make the choice on bug #35757 -- Eric, I believe slamm is away right now so this is going untended -- is this perchance a widget bug, or is it strictly an xpapps thing).
*** Bug 34875 has been marked as a duplicate of this bug. ***
Keywords: nsbeta2
Target Milestone: --- → M17
claudius, do u still see this? I cannot recreate.
Ok...this bug cannot be verified unless the grippy closing problem ( bug 35093) is fixed.marking this as dependent on 35093
Depends on: 35093
Putting on [nsbeta2+] radar for beta2 fix.
Whiteboard: [nsbeta2+]
Status: NEW → ASSIGNED
Depends on: 37835
Whiteboard: [nsbeta2+] → [nsbeta2+] Blocked by 37835
Move to M18 target milestone.
Target Milestone: M17 → M18
verify away, shrir ...
Whiteboard: [nsbeta2+] Blocked by 37835 → [nsbeta2+]
done !! (2000052608)
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
v
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.