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

allow you to specify targetRanges and dataTransfer in InputEventInit #147

Closed
johanneswilm opened this issue Nov 5, 2023 · 1 comment
Closed

Comments

@johanneswilm
Copy link
Contributor

Allowing the specification of targetRanges and dataTransfer has been possible in Firefox and Chromium for some time - but not Webkit. There is now a PR to make this happen in Webkit as well [1].

@whsieh writes:

It seems like the spec doesn't include these two arguments, but testing in Chrome and Firefox, I can see that they both allow you to specify targetRanges and dataTransfer in InputEventInit, so this change would align with Firefox/Chrome. It seems that the spec just needs to be updated.

Note that specifying target ranges has been discussed earlier [2] and it was argued there that the spec now contains everything needed to make dataTransfer/targetRanges part of InputEventInit.

[1] WebKit/WebKit#19346

[2] #47

@johanneswilm johanneswilm added the Agenda+ Queue this item for discussion at the next WG meeting label Nov 5, 2023
@johanneswilm
Copy link
Contributor Author

Fields as specified in input events spec: https://w3c.github.io/input-events/#interface-InputEvent

@johanneswilm johanneswilm removed the Agenda+ Queue this item for discussion at the next WG meeting label Dec 7, 2023
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

1 participant