Confirmed. I minimized the repro a bit more, but same steps - drag 'drag me' onto 'drop zone' and watch the console.


Firefox logs: 'added kind file', 'drop kind file'
Chrome logs: 'added kind file', 'drop kind string'

Deleted: dataTransfer.html 829 bytes

dataTransfer.html 829 bytes View Download

Note that I was testing in 57, so this is not a regression in 59.

Duplicate of issue 438479

This issue is not duplicate of other topics, because:

This issue and issue 438479 has same title but core concern of issue 438479 is async clipboard API. Although
current clipboard API has sync behavior and is based on DataTransfer. The user can use below code instead of canvas.toBlob until committed newly async clipboard interface proposal.

event.clipboardData.items.add(canvas.toDataURL(...), 'text/uri-list');

The issue 438479 is created on 2014.

 Issue 271424  emphasis the DataTransferItemList interface, but it behaves incorrectly according to W3 specification and it is unsolved completely but its status is Fixed?!
The  issue 271424  is created on 2013.

From 2013 till now this implementation has faulty behavior.

The circumstances described are different, but do you believe that the root cause is? Reopening just to be safe, and marking as blocking issue 438479 to retest after that is fixed.

Definitely, DataTransferItemList for Drag & Drop is almost new standard and as I proved, it is not correctly implemented on the Google Chrome.
The fault is still remained in latest version. However  Issue 271424  has been marked as solved.

@pwnall, is this is a dup of 438479?

#7: Yes.