You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The dropzone attribute is being removed from the HTML specification in whatwg/html#2402 and should be removed from WPT. This is not a trivial find-and-remove because we need to make sure that the tests we remove aren't intended to cover other functionality.
For example, Blink had tests that used dropzone and also covered the interaction between DataTransfer.effectAllowed and DataTransfer.dropEffect, which had to be rewritten in https://codereview.chromium.org/2729353002/
This issue will track my efforts to sift through all tests that contain dropzone and update or remove them.
The text was updated successfully, but these errors were encountered:
dropzone failed to get traction among browser implementers. Having it in
the specification is confusing to Web developers who may attempt to use
it, only to discover that it is not supported.
WebKit and Blink implemented a prefixed version, webkitdropzone. The
prefixed version is going away from Blink [1]. WebKit has no objections
to the attribute getting removed from the spec [2].
Fixes#2331. Tests:
* web-platform-tests/wpt#5052
* web-platform-tests/wpt#5053
[1]: https://www.chromestatus.com/feature/5718005866561536
[2]: #2331 (comment)
The
dropzone
attribute is being removed from the HTML specification in whatwg/html#2402 and should be removed from WPT. This is not a trivial find-and-remove because we need to make sure that the tests we remove aren't intended to cover other functionality.For example, Blink had tests that used
dropzone
and also covered the interaction betweenDataTransfer.effectAllowed
andDataTransfer.dropEffect
, which had to be rewritten in https://codereview.chromium.org/2729353002/This issue will track my efforts to sift through all tests that contain
dropzone
and update or remove them.The text was updated successfully, but these errors were encountered: