Closed Bug 95991 Opened 23 years ago Closed 23 years ago

Cant (re)name bookmarks added to Personal toolbar

Categories

(SeaMonkey :: Bookmarks & History, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 68558

People

(Reporter: bugzilla, Assigned: bugs)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.3+) Gecko/20010817 BuildID: 20010817 Cant name bookmarks that I copyed from the adress bar and pasted them to the personal toolbar. Reproducible: Always Steps to Reproduce: 1. Go to http://www.aftonbladet.se 2. Copy the url in the adress bar 3. Paste it in to the personal toolbar. 4. Try renaming (its empty, no name) the bookmark. Actual Results: The propertis tab for the bookmark appears, you type something in the "name" field and press "ok", but nothing happends Expected Results: Entred name should (re)name the bookmark.
I think that this bug might be a dup of bug 90421 (look at the javascript console). Adding a comment in that bug now.
Dont know if it is the same. With todays build 20010820 I cant even paste something in to the toolbar. Getting this error in js-console: Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIRDFContainer.Init]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://communicator/content/bookmarks/bookmarksOverlay.js :: anonymous :: line 511" data: no] Source File: chrome://communicator/content/bookmarks/bookmarksOverlay.js Line: 511
For me with 2001082008 build the errors are just the same as with the 0817. Anyway, marking this bug as new
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** This bug has been marked as a duplicate of 68558 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
mass-verifying Duplicate bugs which haven't changed since 2001.12.31. set your search string in mail to "CitizenGKar" to filter out these messages.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.