Skip to content

Conversation

@roraja
Copy link
Contributor

@roraja roraja commented Nov 27, 2025

This PR adds an explainer documenting the fix for preserving dropEffect values set by web applications during dragover event handlers through to drop events, ensuring compliance with the HTML5 Drag and Drop specification.

What this explainer covers:

  • The specification requirement that dropEffect should reflect the value set during the last dragover or dragenter event when the drop event fires
  • The problem web developers faced when browsers overwrote the application-set dropEffect value before the drop event
  • How this fix enables reliable drag-and-drop implementations where developers can determine the intended operation (copy, move, link) in their drop handlers
  • Real-world use cases including file managers and custom drag-and-drop interfaces

- Chromium Bug: [Issue 40068941](https://issues.chromium.org/issues/40068941)
- Chromium Review: [CL 6818116](https://chromium-review.googlesource.com/c/chromium/src/+/6818116)
- Spec: [HTML5 Drag and Drop Specification](https://www.w3.org/TR/2011/WD-html5-20110113/dnd.html#dndevents)
- Open new issue: [Open New Issue](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?title=%5BPreserveDropEffect%5D+%3CTITLE+HERE%3E)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add label also here so that tracking becomes easy?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants