Closed Bug 80150 Opened 24 years ago Closed 23 years ago

Bookmark gets deleted if droped onto the column picker

Categories

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

x86
Windows 2000

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.9.6

People

(Reporter: cplyon, Assigned: paulkchen)

Details

(Keywords: dataloss)

Attachments

(1 file)

Using build 2001051004 on Win2K Steps to Reproduce: 1. Open Manage Bookmarks window 2. Drag and drop a bookmark onto the column picker Result: The bookmark gets deleted It also generates this error: Error: uncaught exception: [Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIRDFContainer.InsertElementAt]" nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)" location: "JS frame :: chrome://communicator/content/bookmarks/bookmarksDD.js :: anonymous :: line 319" data: no] Source File: chrome://global/content/nsDragAndDrop.js Line: 105 It also generates the error seen in bug 80149. This was originally part of bug 25741.
Marking NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Adding dataloss keyword.
Keywords: dataloss
nav triage team: Marking nsbeta1+, p2, and mozilla1.0
Keywords: nsbeta1+
Priority: -- → P2
Target Milestone: --- → mozilla1.0
dataloss -> moving up to mozilla0.9.5
Target Milestone: mozilla1.0 → mozilla0.9.5
0.9.5 is out the door. bumping TM up by one.
Target Milestone: mozilla0.9.5 → mozilla0.9.6
patch checks to make sure we're not dragging/dropping on head row.
Status: NEW → ASSIGNED
Comment on attachment 53553 [details] [diff] [review] patch to fix r=pchen
Attachment #53553 - Flags: review+
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
Fix checked in.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
mass-verifying claudius' Fixed bugs which haven't changed since 2001.12.31. if you think this particular bug is not fixed, please make sure of the following before reopening: a. retest with a *recent* trunk build. b. query bugzilla to see if there's an existing, open bug (new, reopened, assigned) that covers your issue. c. if this does need to be reopened, make sure there are specific steps to reproduce (unless already provided and up-to-date). thanks! [set your search string in mail to "AmbassadorKoshNaranek" 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.

Attachment

General

Created:
Updated:
Size: