Closed Bug 54253 Opened 25 years ago Closed 25 years ago

Drag and Drop causes data loss

Categories

(Core :: DOM: Editor, defect, P1)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: kinmoz, Assigned: anthonyd)

Details

(Keywords: dataloss, regression, Whiteboard: [nsbeta3-][p:1][rtm++]FIX IN HAND, PATCH)

Attachments

(3 files)

Startup a blank editor. Type the following into the editor: This is a test Now select " is a", then click and drag the selection to any point after the word "test" and then let go of the mouse button to drop it. " is a" disappears and is not added after "test" so the content now looks like: This test It should look like: this test is a
Adding nsbeta3, rtm and dataloss keywords.
Keywords: dataloss, nsbeta3, rtm
OS: Windows NT → All
Priority: P3 → P1
Hardware: PC → All
Target Milestone: --- → M18
Forgot to add regression keyword.
Keywords: regression
This is a regression and when users select drag & drop and drop in the same window the selected text gets deleted and on drop the data is not dropped.
Whiteboard: [nsbeta3+][p:1]
Marking nsbeta3- as I don't believe that this is a stopper for PR3 (undo - modulo the double undo bug - retrieves the data). The bug is already nominated for rtm.
Whiteboard: [nsbeta3+][p:1] → [nsbeta3-][p:1]
reassigning to brade
Assignee: anthonyd → brade
drag and drop is a frequently used function, users will expect the function to be usable and reliable. Many users are unaware of undo/redo and multiple undo/redo. Kathy, please include the required information per the rtm checkin rules
Whiteboard: [nsbeta3-][p:1] → [nsbeta3-][p:1][rtm+ NEED INFO]
Target Milestone: M18 → M19
re-assigning to myself. anthonyd
Assignee: brade → anthonyd
PDT agrees [rtm need info] until patch and code reviews are available.
Whiteboard: [nsbeta3-][p:1][rtm+ NEED INFO] → [nsbeta3-][p:1][rtm NEED INFO]
Keywords: mailtrack
Attached patch fix for bug.Splinter Review
adding ken and simon for approval and review. please? thanks, anthonyd
Status: NEW → ASSIGNED
Whiteboard: [nsbeta3-][p:1][rtm NEED INFO] → [nsbeta3-][p:1][rtm]FIX IN HAND, PATCH
This is a bad code pattern: if (NS_FAILED(rv) || !newSelectionOffset) return rv?rv:NS_ERROR_FAILURE; since NS_FAILED(rv) != (rv == 0) (i.e. non-zero rv's can mean success). Better to write this out in full, or just skip the rv test. I'd also like to see a description of what the patch is doing.
kin will re-review and give me approval. anthonyd
Whiteboard: [nsbeta3-][p:1][rtm]FIX IN HAND, PATCH → [nsbeta3-][p:1][rtm NEED INFO]FIX IN HAND, PATCH
simon, I changed that checking condition in the latest patch, and I added a comment to explain what the patch does into the patch itself. anthonyd
r=sfraser
pdt team: got everything I need for this: sr=kin r=sfraser a=kin patch is attached anthonyd requesting rtm++
sent email topdt team requesting rtm++ status
Whiteboard: [nsbeta3-][p:1][rtm NEED INFO]FIX IN HAND, PATCH → [nsbeta3-][p:1][rtm+]FIX IN HAND, PATCH
rtm++
Whiteboard: [nsbeta3-][p:1][rtm+]FIX IN HAND, PATCH → [nsbeta3-][p:1][rtm++]FIX IN HAND, PATCH
fix checked in to both branch and trunk. anthonyd
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
verified in 10/10 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: