Closed Bug 403908 Opened 18 years ago Closed 18 years ago

[10.4] Application (Firefox/SeaMonkey) menu out of place

Categories

(Core :: Widget: Cocoa, defect, P1)

PowerPC
macOS
defect

Tracking

()

VERIFIED DUPLICATE of bug 403967

People

(Reporter: quicksilver8, Assigned: jaas)

References

Details

(Keywords: regression)

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O 10.4; rv:1.9b2pre) Gecko/2007111501 SeaMonkey/2.0a1pre Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O 10.4; rv:1.9b2pre) Gecko/2007111501 SeaMonkey/2.0a1pre With today's build, SeaMonkey menu, normally the first on the left within menubar, appears at the end, on the right. Menu items work fine, but menu place is wrong. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Ditto with Firefox; hopefully one fix fixes both.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee: nobody → joshmoz
Severity: normal → major
Component: Build Config → Widget: Cocoa
Product: Mozilla Application Suite → Core
QA Contact: build-config → cocoa
Version: unspecified → Trunk
Flags: blocking1.9?
Summary: SeaMonkey menu out of place → Application (Firefox/SeaMonkey) menu out of place
I don't see this on 10.5, but it's there on 10.4.
Summary: Application (Firefox/SeaMonkey) menu out of place → [10.4] Application (Firefox/SeaMonkey) menu out of place
Flags: blocking1.9? → blocking1.9+
Priority: -- → P1
Woah. And on 10.5, I'm not sure how yet, but I had three File menus. I'm still looking for ways to reproduce that.
(In reply to comment #4) > Woah. And on 10.5, I'm not sure how yet, but I had three File menus. I'm still > looking for ways to reproduce that. Filed bug 403967 for that.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Josh, just to be clear, this bug is about the application menu (Firefox menu) not being placed right. That's fixed by your patch in bug 403967?
Probably. If I'm wrong feel free to reopen.
I just tested today's nightly of SeaMonkey on 10.4 and 10.5, problem is fixed.
Verified dup
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.