dataTransfer.dropEffect value is always none in drop and dragend handlers

Not reproducible Issue #14368369


Yaroslav A.
Oct 25, 2017
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Check this JSFiddle:

It implements basic HTML5 Drag’n’drop. The problem is that event.dataTransfer.dropEffect is always set to none in the drop and dragend event handlers.

  1. Click Run
  2. Drag “This element is draggable.” into “Drop zone”
  3. Observe console output.
dragstart none
dragover move (n times)
drop none (should be "drop move")
dragend none (should be "dragend move")

The expected behaviour is observed in Chrome 62, Safari 11 and Firefox 55.

According to spec the dropEffect property should be set to current drag operation.

Set the dropEffect attribute to the value corresponding to the current drag operation if e is drop or dragend

Where linked section outlines in step 3 - 3 that:

Otherwise (if the dragover event is canceled), set the current drag operation based on the values of the effectAllowed and dropEffect attributes of the DragEvent object’s dataTransfer object as they stood after the event dispatch finished, as per the following table: […]


1 attachment

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “James M.”

  • Hello,

    Thank you for providing this information about the issue. After thorough testing, we are unable to reproduce this problem in Edge. I have attached a screenshot of the console log; it is same for 15063, 16299 and 17017.

    Please review ours, then share a screenshot of your console log for further investigation.

    Best Wishes,
    The MS Edge Team

  • I’ve run linked fiddle on several different computers and now I get same (correct) behavior as you described in the comment. I don’t know how it is possible, because it didn’t work dozens of times, when I was trying to figure out how to make it work and while preparing bug report.

    Unfortunately it still doesn’t work in the real application (which is built using Angular). Maybe it is somehow related to creating draggable/drop zone elements dynamically… I remember having trouble with this in the past. I’ll try to figure out what I could have missed and get back with more information.

    Sorry for the confusion.

  • Microsoft Edge Team

    Changed Status to “Not reproducible”

  • Hello,

    Thank you for providing an update. No problem, we will close this case for now, but please reopen it when you can provide new information about your problem. We look forward to all your feedback regarding Microsoft Edge.

    Best Wishes,
    The MS Edge Team

You need to sign in to your Microsoft account to add a comment.

Sign in