Open Bug 87515 Opened 24 years ago Updated 8 years ago

Bookmarks menu missing when the Bookmarks window has focus

Categories

(SeaMonkey :: Bookmarks & History, defect, P5)

Product:
SeaMonkey
Component:
Bookmarks & History
Platform:
All
macOS
Type:
defect

Tracking

(Not tracked)

People

(Reporter: mpt, Unassigned)

References

Details

(Whiteboard: [2012 Fall Equinox])

To reproduce: * Open the Bookmarks window. * Try to go to a bookmark in the `Bookmarks' menu. What should happen: * You can. What actually happens: * You can't. Problem occurs with: * Build 2001062105, Mac OS 9.1 Problem does not occur with: * Internet Explorer 5.0 for Mac OS * Opera 5.0b1 for Mac OS * iCab pre2.5.1
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Paul Chen is now taking Bookmarks bugs. For your convenience, you can filter email notifications caused by this by searching for 'ilikegoats'.
Assignee: ben → pchen
Status: ASSIGNED → NEW
Mass move Ben's bugs dumped on me marked future with p5 to get off my untriaged radar. You can filter out this email by looking for "ironstomachaussie"
Priority: -- → P5
mass reassign of pchen bookmark bugs to ben
Assignee: pchen → ben
Worksforme with 2002042608 trunk Windows 98. Are you still seeing this?
Blocks: 140346
*** Bug 133898 has been marked as a duplicate of this bug. ***
WFM 2002110708. Resolving as such due to this, comment 4 and no response to Andrew's question
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
hello? anyone home? pay attention now. Open the bookmarks window now look at the menu bar. i have: > file edit view tools window help <Jan> me too whereas navigator has: > file edit view go bookmarks tools window help debug qa this bug is about the fact that there is no 'bookmarks' menu in the bookmarks window. This bug was reported by a mac user because on macos there is a single menubar and it isn't supposed to change as you select different windows in a single application. (The fact that mail and navigator are part of the same app is considered a bug so mail only needs to be split out of mozilla and then remain internally consistent.) fwiw, this thing isn't fixed in 2002110408, and it isn't fixed in whatever more current build jan has.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Blocks: 118396
Changing component, reassigning to default owner of new component.
Assignee: ben → hyatt
Status: REOPENED → NEW
Component: Bookmarks → XP Toolkit/Widgets: Menus
QA Contact: claudius → shrir
this bug belongs to _bookmarks_, because it's a bookmarks window which lacks this menu. the xp toolkit/widgets components are _only_ for bugs in the actual menu implementation. actual menus belong in the component they are part of. torben please don't touch bugs that you have no clue of. thanks. moving back to where it belongs, in the hope that it stays there.
Assignee: hyatt → ben
Component: XP Toolkit/Widgets: Menus → Bookmarks
QA Contact: shrir → claudius
re comment 7 > (The fact that mail and navigator are part of the same app is > considered a bug so mail only needs to be split out of mozilla > and then remain internally consistent.) so why is bug 133898 dupe of this? and how about bug 150516, bug 189486, bug 165790, and bug 189486? Does this bug only applies to bookmarks manager only but not to default application menu? and why does this bug block bug 140346?
This bug is targeted at a Mac classic platform/OS, which is no longer supported by mozilla.org. Please re-target it to another platform/OS if this bug applies there as well or resolve this bug. I will resolve this bug as WONTFIX in four weeks if no action has been taken. To filter this and similar messages out, please filter for "mac_cla_reorg".
OS: Mac System 9.x → MacOS X
Mass reassign of my non-Firefox bugs to ben_seamonkey@hotmail.com
Assignee: bugs → ben_seamonkey
See also bug 247041.
Product: Browser → Seamonkey
Assignee: ben_seamonkey → nobody
QA Contact: claudius → bookmarks
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Still happens in 2.x (nightly)
Status: UNCONFIRMED → NEW
Is this still reproducible in modern SeaMonkey versions?
Whiteboard: [2012 Fall Equinox]
(In reply to Phoenix from comment #22) > Is this still reproducible in modern SeaMonkey versions? Yes, it is.
Stefan aside from ui guidelines should this be really implemented? As an occasional osx user I would vote for wontfix. We probably have a bunch of other cases where the menu changes and in most of them it imho makes no sense to show the whole navigator or application menu.
Severity: normal → minor
Flags: needinfo?(stefanh)
Hardware: PowerPC → All
Target Milestone: Future → ---
The idea of having different menubars for different windows is really a win/nix thing ;-) But of course, this is some work - I doubt anyone would get to this soon. I don't want it to be wontfixed, though - I do think it's a valid bug.
Flags: needinfo?(stefanh)
You need to log in before you can comment on or make changes to this bug.