Primary eng (and PM) emails
The dropzone global attribute [1, 2] was introduced by the HTML5 drag and drop specification as a declarative method for specifying an HTML element's willingness to be the target of a drag-and-drop operation, as well as the content types that can be dropped onto the element, and the operation (copy/move/link) that would result from dropping something onto the element. No browser has implemented the unprefixed version. Blink and WebKit implement a prefixed form of the attribute, webkitdropzone.
Given that the attribute failed to gain traction with other browsers, I would like to immediately remove it from our implementation, to reduce the risk of having Web content grow to depend on it.
This is a prefixed attribute that will never be standardized. The standardized version of the attribute is failing to gain traction from other browser implementers. Therefore, I would like to remove the attribute before Web content starts depending on it.
Compatibility And Interoperability Risk
No browser currently supports the un-prefixed version of the attribute .
Our implementation was incorrect until M57 [2, 3], so webkitdropzone could not be used to accept file drops on sites (it only worked for file: origins). We didn't receive any complaints, and I only learned about the bug while trying to fix an issue [4, 5] whose code happened to be related to the webkitdropzone implementation.
Given these issues, applications targeting the Web platform (i.e. Firefox, Edge, IE) cannot rely on dropzone / webkitdropzone support, and must declare the willingness to accept drag-and-drop operations via the imperative API offered by the dragenter and dragover event handlers .
Edge: No signals
Firefox: Not supported - bug comment suggests they're unhappy with the spec https://bugzilla.mozilla.org/show_bug.cgi?id=723008
Safari: Public support - rniwa opened a bug on Firefox's tracker asking for the attribute to be implemented https://bugzilla.mozilla.org/show_bug.cgi?id=723008
Web developers: No signals
Alternative implementation suggestion for web developers
Applications targeting the Web platform should declare their willingness to accept drag-and-drop operations via the imperative API offered by the dragenter and dragover event handlers.
Usage information from UseCounter
The usage appears to be at 0.07% currently. However, based on the HTTPArchive data below, I'd guess that most of it is feature detection.
Looking at HTTPArchive yielded the following results:
https://globalchallenges.org/main.5bd764e65b815c6d94e3.bundle.js -- in list of attributes, doesn't appear to be used
https://questions.learnosity.com/v2.97.0/dist/api.js -- check for prefixed versions of dropzone in all browsers
OWP launch tracking bug
Entry on the feature dashboard
Requesting approval to remove too?
Do you think we should also yank this unprefixed attribute from the HTML spec as well? If we start that process now, it'd be a chance for others to protest if they actually did want to implement and ship this but haven't gotten around to it yet.
The number of sites in httparchive is remarkably small, so this seems rather low risk. Almost certainly the counter is being hit by accident by enumeration, which is a common problem with attributes. In https://bigquery.cloud.google.com:443/savedquery/762219082167:20eb08762edc47178a5e7caba3170864 there are 500 hits of the use counter, if you're curious about how that might happen. I didn't look too closely, and one can safely assume this sites will not be breaking.Can you write an example code snippet for how to migrate from webkitdropzone to dragenter + dragover? Something that can be copy-pasted can really help when sites are suddenly broken.
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.