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

July 29th F2F Agenda Item - Data and dataTransfer attributes #139

Closed
gked opened this issue Jul 29, 2016 · 6 comments
Closed

July 29th F2F Agenda Item - Data and dataTransfer attributes #139

gked opened this issue Jul 29, 2016 · 6 comments

Comments

@gked
Copy link

gked commented Jul 29, 2016

What should the relation between the two be? See Issue 131.

@gked
Copy link
Author

gked commented Jul 29, 2016

We'll keep data only for insertText with dataTransfer set to null input type and for other input types use dataTransfer and data set to null.

@garykac
Copy link
Member

garykac commented Aug 1, 2016

Summary:

  • cut/copy/paste/drag/drop: dataTransfer=, data=null
  • insertText: data=, dataTransfer=null
  • other beforeinputs have both of these these = null

Would be nice to express in a table as was done for pointerevents.

@johanneswilm
Copy link
Contributor

@garykac Earlier, we decided to remove the copy beforeinput event, right?

@gked
Copy link
Author

gked commented Aug 15, 2016

@johanneswilm,
Right. The reason from what I remember is that Input event should be paired with beforeInput event.

@johanneswilm
Copy link
Contributor

@gked: Yepp, that's also what I remembered. I just noted @garykac had added it again in the overview above, so I wanted to make sure we are on the same page with this. I did remove it from the spec, but we can always add it again if we change our minds.

@johanneswilm
Copy link
Contributor

This issue was moved to w3c/input-events#16

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

No branches or pull requests

3 participants