Closed Bug 355802 Opened 19 years ago Closed 18 years ago

[Cocoa] Missing SeaMonkey Menu Entries

Categories

(SeaMonkey :: General, defect)

PowerPC
macOS
defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: timd_huang, Assigned: stefanh)

References

Details

(Keywords: regression)

Attachments

(1 file, 2 obsolete files)

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20061006 SeaMonkey/1.5a Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20061006 SeaMonkey/1.5a Since about Oct. 01, the "SeaMonkey" Menu does not contain several entries, such as Hide SeaMonkey. The only way to hid SeaMonkey application is to click the yellow button on the upper left corner for each window. Pain on you know where. Reproducible: Always Steps to Reproduce: 1. Open the latest nightly build. 2. Look at the "SeaMonkey" menu. 3. Actual Results: Only three entries: About SeaMonkey, Preference, and Quit. All others are missing.
Most probably caused by bug 326469. See also bug 355797.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
Summary: Missing SeaMonkey Menu Entries → [Cocoa] Missing SeaMonkey Menu Entries
Blocks: 326469
(In reply to comment #1) > Most probably caused by bug 326469. See also bug 355797. > Those menuitems needs to be in the DOM (see the documentation in nsMenuBarX.mm line 614 and on).
*** Bug 357498 has been marked as a duplicate of this bug. ***
Attached patch work in progress (obsolete) — Splinter Review
Attaching a patch that I've had in my tree for some time now. It's not 100% tested, but the patch will add the missing menuitems (and fix the shortcuts). Unfortunately, "About" and "Preferences..." doesn't work with Venkman. Trying to open preferences from the menu with Venkman open also results in an assertion: ###!!! ASSERTION: Carbon event for menu hit not sent!: 'err == noErr', file /Users/Stefan/mozilla-debug/mozilla/widget/src/cocoa/nsMenuBarX.mm, line 1115
Flags: blocking-seamonkey1.5a?
I have a patch for this. But I think the fix for this will be a lot cleaner after Josh have landed some stuff (like the patch in bug 368911).
Assignee: general → stefanh
Attached patch Fix app menuitems and shortcuts (obsolete) — Splinter Review
This should get us a working app menu again. The pref menuitem will now work in all windows - even if they don't contain the menuitem. What happens is that if the window doesn't have a pref menuitem we'll use the content node from hiddenwindow. The only small issue with this is that we'll open the navigator prefs in a DOMi window/Password Manger/etc opened from Composer, MailNews etc. Mnyromyr and I had a chat about the modifiers yesterday. In toolkit they're localized (except the Quit command). To make a long story short: Since there might be a tiny risk that some locale (that we don't know of) *might* have different modifiers in the app menu it can't be wrong to make them localizable.
Attachment #253946 - Attachment is obsolete: true
Attachment #258717 - Flags: review?(mnyromyr)
Status: NEW → ASSIGNED
Comment on attachment 258717 [details] [diff] [review] Fix app menuitems and shortcuts > <menupopup id="menu_FilePopup"> ... >+ <!-- These 5 menuitems (and the menu_preferences menuitem above) are added >+ to the Application menu. They just need to be in the DOM, widget code >+ does the rest --> The way how this is done by the Mac widget code is really oh so hacky, but we seem to have to live with it. :-| >Index: suite/locales/en-US/chrome/common/mac/platformCommunicatorOverlay.dtd >=================================================================== >+<!-- LOCALIZATION NOTE: FILE Do not translate all the Cmd.key --> Just a nit, since you're touching this actually unrelated comment: it's still as incomprehensible as before - I had to read it a couple of times, in context, before understanding it. I'd suggest something like: <!-- LOCALIZATION NOTE: FILE Do not translate all the entities ending with Cmd.key -->
Attachment #258717 - Flags: review?(mnyromyr) → review+
> I'd suggest something like: > <!-- LOCALIZATION NOTE: FILE Do not translate all the entities ending with > Cmd.key --> > Yeah, that'll make it more clear.
Same as previous patch, just addressing Karsten's suggestion.
Attachment #258717 - Attachment is obsolete: true
Attachment #259546 - Flags: superreview?(neil)
Attachment #259546 - Flags: review+
Attachment #259546 - Flags: superreview?(neil) → superreview+
Landed on trunk by ajschult (thanks!)
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Flags: blocking-seamonkey1.5a?
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: