Closed Bug 139741 Opened 22 years ago Closed 22 years ago

Sidebar Is Empty at startup

Categories

(SeaMonkey :: Sidebar, defect)

defect
Not set
critical

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: bugs, Assigned: samir_bugzilla)

Details

Steps to reproduce:

1) Start Mozilla
2) Ensure the sidebar is visible
3) Close the sidebar using the close button on the personal toolbar
4) Quit
5) Restart
6) Click the sidebar button on the personal toolbar

Expected results:
- sidebar opens, with my panels

Actual results:
- blank sidebar opens. No amount of opening and closing the sidebar using the
button will fix this. Closing and then opening the sidebar with F9 seems to
work, though. 

Also, if you click on the "Tabs" dropdown, you'll get an assert in debug builds
and an empty panel list, until the sidebar has been successfully populated,
either by hitting F9, or by shutting down with the sidebar in an open state,
such that it is forced to load on startup.
Severity: normal → critical
Keywords: nsbeta1
Tracy can you reproduce ?
Keywords: smoketest
yes, I saw this on windows commercial trunk build 2002-04-24-06-trunk
confirming, I also see this in 4/24 trunk build.
This is not new... I saw this weeks ago.
This patch is not on the branch yet.  So nsbeta1 is irrelevant.
Keywords: nsbeta1
This is not a smoketest blocker: if you create a new profile and don't use this
button you won't run into *any* problems.  If you do use this button you and get
into the state where there is no sidebar the simlpe work around is to hit F9
twice to close and reopen the sidebar.

Furthermore, this is not a new bug (just exposed by the new sidebar toolbar
button): if you had a profile that had collapsed the sidebar and restarted
mozilla, then tried to drag open the sidebar using the grippy you would run into
the same issue.  
Keywords: smoketest
I've always collapsed sidebar when I don't need anything of it, so it's always
collapsed at startup, and I've been seeing this for a while...
This is definately not caused by this new button but has been existing some time
now, I thought it might have started to occur when we had those iframe loading
changes but I'm not completely sure....
It seems that opening the sidebar by hitting F9 (and probably the menu 
item) causes the panel set to be loaded. The button does not seem to 
invoke that load. Hence, I think this is new. 
this is happening cross platform
OS: Windows XP → All
Hardware: PC → All
Keywords: nsbeta1
Removing nomination since this is being caused by the new toggle button on the
personal toolbar which is only on the trunk.
Keywords: nsbeta1
I have seen this bug for months, I have just not bothered to file it, because I
thought "this bug _has_ to be reported already". I guess I was wrong, and I
regret not having filed this issue earlier.

I'm on win2k, and upgrade my build every day. This issue has been coming and
going for many months, and I do not know how to reproduce it.

Every time I upgrade, I unzip mozilla into a new directory, so there should be
no conflicts.

Hmm.. I'm sorry, I just read the initial description now, when writing this
comment. My issue is that when I start mozilla, the sidebar is empty, I don't
need to click the button on the personal toolbar in order to 'empty' it.

But I guess this is related somehow.
The sidebar ``toggle'' button on the personal toolbar has been backed out. 
Ben's original steps refer to it hence this bug can now be closed.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
As Brian Nesse stated, this was around well before the sidebar toggle button was 
put in.  I'd be surprised if this is really fixed by backign that out.  We'll 
verify next test.
Tracy,
As I said in my repotr: I am marking the originally reported bug fixed which
involves the personal toolbar button which should be gone in tonight's builds
(or any builds after 8am today).  So reopening this will be bogus unless the
toolbar button is not gone.  :o)
verified in 4/29 trunk build.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.