190264 - No context menu in bookmarks tab in sidebar

Status: VERIFIED FIXED

(SeaMonkey :: Sidebar, defect)

Description

[Christian Weisel]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030122
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030122

There is no right click context menu in the bookmarks sidebar tab! You just see
a small grey box which looks like a corner of a menu

Reproducible: Always

Steps to Reproduce:
1. Open Sidebar
2. Go to bookmark panel
3. Right click on a bookmark

Actual Results:  
You will see a small empty part of a menu neer the mouse pointer

Expected Results:  
A right click menu like in bookmar manager (or no menu at all).

Comment 1

[R.K.Aa.]

yesterdays trunk CVS build on Linux:
Context menus are also empty in personal toolbar (bug 190232) and Bookmark Manager.

Comment 2

[R.K.Aa.]

Appears in JS console when right-clicking in sidehar:

Error: this.db.GetTarget(rSource, rName, true) has no properties
Source File:
chrome://communicator/content/bookmarks/bookmarks.xml#bookmarks-tree.getCommandName()
Line: 16

This appears when right-clicking on personal toolbar:
Error: aNodeID is not defined
Source File: chrome://communicator/content/bookmarks/bookmarksOverlay.js
Line: 288

And this appears when right-clicking in Bookmark Manager:
Error: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIStringBundle.GetStringFromName]"  nsresult:
"0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame ::
chrome://communicator/content/bookmarks/bookmarks.js :: Startup :: line 64" 
data: no]

Error: this.db.GetTarget(rSource, rName, true) has no properties
Source File:
chrome://communicator/content/bookmarks/bookmarks.xml#bookmarks-tree.getCommandName()
Line: 16

Seems to be the stringbundle bug that caused some horkage yesterday.
Adding dependency.

*** This bug has been marked as a duplicate of 190256 ***

Comment 3

[R.K.Aa.]

sorry dependency... not dup

Comment 4

[Andreas Kunz]

...and it works now that the other bug has the fix in.
(2003012308)

Comment 5

[R.K.Aa.]

yes - the patch there fixed it, resolving as such

Comment 6

[Grace Bush]

verified all platforms 3/21 builds