Closed Bug 87414 Opened 24 years ago Closed 23 years ago

Sidebar panels are not showing in trunk (0.9.3) builds

Categories

(SeaMonkey :: Sidebar, defect, P3)

Product:
SeaMonkey
Component:
Sidebar
Platform:
x86
Windows 2000
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME
Milestone:
mozilla1.2alpha

People

(Reporter: slogan, Assigned: matt)

Details

(Whiteboard: investigating)

Multiple people are seeing problems with sidebar panels not showing in the browser or mail news sidebar. Those that don't work display "This tab is not available right now". This regression probably happened the day 0.9.3 opened, and implies someone did not run basic tests to verify the submission.
Nominating
Severity: normal → blocker
Keywords: nsbeta1
I get a bunch of asserts before seeing the same problem. Here are the ones that look suspicious-- nsFrameFrame.cpp:1240, and some more in nsHTMLFrameInnerFrame(?)
My build on Linux from the trunk: checkout start: Sat Jun 23 09:00:03 BST 2001 works fine with all the default sidebar panels. This is either a more specific per-user thing or platform-specific.
If this does not happen on the branch, it is not an rtm stopper, but we shd kill this trunk regression asap as it is very basic functionality. Matt can you please take a look. thanks, Vishy
Priority: -- → P1
Target Milestone: --- → mozilla0.9.3
updating tree
Whiteboard: investigating
built a depend build. Does not show up on it. Clobbering...
downloaded trunk build and tried it on NT4.0 and it works fine. Is this an windows 2000 only problem or are there specific tabs you are looking at?
Moving down from blocker status. Reproduced this on gagans machine. This seems to be only when a mozilla user has a sidebar panel that is local that does not exist. So mostly the only time you see this but is when you have a netscape profile and open up mozilla. When you open the netscape local panel it gives this assert. Aparently once and awhile you also do not get the other sidebar panels but we where not able to reproduce this when we tested it several times.
Severity: blocker → critical
nav triage team: Matt, can you talk to Syd about whether this is the case his machine since he's the reporter?
Perhaps this is the problem -- after reading this I tried a new profile and it seemed ok. Still, I was doing nothing more than upgrading my nightly (commercial -> commercial). Should not have affected me in this way.
nav triage team: Forgot to set nsbeta1+
Keywords: nsbeta1 → nsbeta1+
nav triage team: Although annoying, there's the ol' "create a new profile" workaround ;-), and we don't expect it to be too much of a problem for regular NS users (all 50 of them left on the planet), so marking p3, major, and mozilla1.2
Severity: critical → major
Priority: P1 → P3
Target Milestone: mozilla0.9.3 → mozilla1.2
wfm
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
verified.
Status: RESOLVED → VERIFIED
verified.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.