Closed Bug 29251 Opened 25 years ago Closed 25 years ago

Invoking any window from menus or toolbar does not work

Categories

(SeaMonkey :: General, defect, P3)

x86
Windows 98
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: sujay, Assigned: amusil)

References

Details

(Keywords: platform-parity, regression, smoketest, Whiteboard: Fix ready)

using 2/25 build of mozilla build = 1999122808

1) launch mozilla
2) launch editor from tasks menu.

it doesn't come up.

seems to come up on linux....windows only...will try Mac when it comes out.
blocker
Severity: normal → blocker
marking Ender blocker in status summary
Whiteboard: EB
Summary
Summary: [PP] editor doesn't launch for windows → [PP] Tasks menu does not work
linux and mac work....this problem is windows only...
*** Bug 29252 has been marked as a duplicate of this bug. ***
This is also on WinNT.  It's on the Netscape commercial builds only.

This problem is more general than just the Tasks menu.  No subsequent window can 
be brought up via the menu item or the toolbar button (ie. in mail, can't bring 
up new message window)
Summary: [PP] Tasks menu does not work → Invoking any window from menus or toolbar does not work
This is Browser-General...it will need to be verified in all Tasks once fixed.  
Adding shrir.
Component: Editor → Browser-General
From looking at the cvs logs, this is most likely due to law's checkin last 
night.

Reassigning to him.
Assignee: leaf → law
Target Milestone: M14
Update:  I tried the commercial build in the backup directory too it's not 
working, but the mozilla build using the .zip file works.
Over to you Alex ... (and thanks) ...
Assignee: law → amusil
I have a fix.  Looks like an empty style sheet was screwing things up.
Status: NEW → ASSIGNED
Whiteboard: EB → Fix ready
*** Bug 29254 has been marked as a duplicate of this bug. ***
checked in
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
verified in 2/25 evening build ...
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.