78689 - Element receiving drag events incorrectly identififies the flavour of the content being dragged over.

Status: RESOLVED WONTFIX

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

Description

[William Cook]

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
BuildID:    -

I am using the nsDragAndDrop.js wrapper for handling drag events.

I have an element that needs to do different things depending on the flavour of 
the data that is being dragged onto it.  As long as the transfer data is of a 
type that is suported by the element receiving the drag/drop then the element 
thinks that the the flavour of the transfer data is whatever is first in the 
list of supported flavours for that element.

For example,  if you can have three different drag sessions of flavours a, b 
and c and an element that supports flavours [a ,b] then when either flavour a 
or b is dragged over the element it will report the flavour as a (first in the 
list of supported flavours).  Flavour c will be correctly identified as not 
supported.  If, the supported flavours are switched to [b,a] then on dragging 
flavours a or b over the element their flavours will now both be given as b.

Reproducible: Always
Steps to Reproduce:
1.  Create an element that supports 2 or 3 different flavours.
2.  Drag over this element some transfer data with a flavour 
    that is supported by this element.


Actual Results:  Whatever (supported) flavour is dragged over, the element 
thinks that flavour type is the first in the list of supported flavours.

Expected Results:  The element should pick up on the flavour of the transfer 
data correctly.

Text file containg xul/js to follow...

Comment 1

[William Cook]

Attachment: Example XUL and js.

Comment 2

[Blake Ross]

-> Ben

Comment 3

[Terri Preston]

qa contact -> pmac

Comment 4

[Neil Deakin]

The new drag and drop api added in bug 356295 makes fixing this unnecessary.