Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drag and drop spec allows multiple values for dropEffect which might cause browsers to behave differently. #10335

Open
ragoulik opened this issue May 8, 2024 · 0 comments

Comments

@ragoulik
Copy link

ragoulik commented May 8, 2024

The drag and drop spec specifies that UAs can choose the value of the dropEffect attribute from multiple possible options in certain cases. For the dragenter and dragover events, dropEffect is set based on effectAllowed, which can include multiple possible effects (https://html.spec.whatwg.org/multipage/dnd.html#dropEffect-initialisation). For the dragend and drop events, dropEffect is set based on the current user selection and the spec allows multiple possible effects under certain conditions (https://html.spec.whatwg.org/multipage/dnd.html#current-drag-operation:~:text=Set%20the%20current%20drag%20operation%20to%20either%20%22copy%22%20or%20%22move%22%2C%20as%20appropriate%20given%20the%20platform%20conventions). Should the spec be updated to specify a particular dropEffect value that UAs must choose in order to guarantee interop?

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

No branches or pull requests

3 participants
@sanketj @ragoulik and others