H�kan, As far as I can see there is no feedback to the drag source when a drop has occurred. So if the user modifies the drag from a copy to a move by holding down a modifier key how do you tell?
What am I missing? Is it the case that two drop events occur? So a drag observer on the source and on the target both receive drop notifications? As an alternative, I tried to pass the current window as flavour data - but this fails completely. The intention here was to determine the source of the drag and to setup communication via a known callback function. Unfortunately, the object returned in the drop(.. dropdata..) method: dropdata.supports will not QI to the dropData.dataIIDKey given in the flavour object (nsIDOMWindow). It has been reduced to a XPCWrappedNative_NoHelper which seems to have no properties and will not QI to any of the available Components.interfaces... IIDs. I hit this same problem recently trying to get nsITransactionManager to work with Javascript defined transaction objects. Is D&D still hard wired for string, file and URL types only?
