-
Notifications
You must be signed in to change notification settings - Fork 17
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
[beforeinput] Rename drag&drop to deleteByDrag&insertFromDrop #19
Comments
Right. What about the dataTransfer object? Should we keep that? In some ways it seems to be similar to clipboard operations. |
From @choniong on August 24, 2016 15:58 I would imagine we could have:
Does that sounds reasonable? But for
e.g. The raw data could be I would vote for |
Hey, yes, it definitely needs to be 1 as the JS may decide to do something completely different with it and it should have access to the most "original" version of the data available. Did you guys come to a conclusion on whether or not we can create both the dragend- and drop-based beforeinput events? If I recall correctly the plan was for the Chrome team to check their source code on whether it's viable to have both events. |
From @choniong on August 24, 2016 15:17
We should use the name
deleteByDrag
&insertFromDrop
to make it clear that the event is only for DOM modification. (e.g. PreventingdeleteByDrag
won't stop thedrag&drop
process)Background:
Assume we all agree that
InputEvent
should only focus on DOM modification w3c/editing#144 (comment), and we are renamingcut
&paste
todeleteByCut
&insertFromPaste
.Copied from original issue: w3c/editing#147
The text was updated successfully, but these errors were encountered: