Closed Bug 136265 Opened 24 years ago Closed 17 years ago

RFE: A way to signal the source of Drag and Drop that drop has occurred.

Categories

(Core :: DOM: Copy & Paste and Drag & Drop, enhancement)

x86
Windows 2000
enhancement
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: pwilson, Unassigned)

References

Details

I may be missing something obvious, but I can find no way to signal the source of a drag operation that a drop has occurred. As a use case try the following: Drag a range of xml content from one editor window to another instance in another editor window. On drop: The source window needs to remove the range from its document and update its undo state. The targetwindow needs to insert the range into its document and update its independent undo state. Of course the source and target may be the same window. I am currently forced to cache data about the drag operation in global variables and to invoke callbacks on the source window. Because it is the same application I can make private arrangements which would be impossible with applications from different vendors. The target window should not have to know about every possible drag source. In my opinion the dragobserver helper and underlying interfaces need to be extended to supply a optional ondroptarget function as part of the dragstart operation. The drop action (MOVE,COPY,LINK),and the drop window should be parameters to the callback.
-> XP Apps: Drag and Drop. Hopefully somebody there can confirm or dupe this.
Assignee: Matti → blaker
Component: Browser-General → XP Apps: Drag and Drop
QA Contact: imajes-qa → tpreston
Couldn't find any dupes... confirming.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
qa contact -> pmac
QA Contact: tpreston → pmac
Assignee: bross2 → nobody
QA Contact: pmac
Fixed through bug 356295, i think.
Status: NEW → RESOLVED
Closed: 17 years ago
Depends on: 356295
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.