Contact emails
prana...@microsoft.com
Specification
https://w3c.github.io/input-events/#dom-inputevent-datatransfer
Summary
Populate the dataTransfer property on input events with inputType of insertFromPaste, insertFromDrop, and insertReplacementText to provide access to clipboard and drag-drop data during editing operations in contenteditable elements.
The dataTransfer object contains the same data that was available during the beforeinput event.
This feature only applies to contenteditable elements. For form controls (textarea, input), the behavior remains unchanged - the data property contains the inserted text and dataTransfer remains null.
Both Safari and Firefox already support this functionality. Chromium adopting this feature will enhance interoperability across browsers, providing a more consistent experience for web authors.
Blink component
Blink>Editing>InputEvent
Web Feature ID
input-event
TAG review
None
TAG review status
Not applicable
Risks
Debuggability
No additional Devtools support is needed to debug this feature.
Will this feature be supported on all six Blink platforms
(Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
Yes
Yes
https://wpt.fyi/results/editing/other/data_transfer_on_input_event_with_insertfrompaste_type.html?label=experimental&label=master&aligned
https://wpt.live/html/editing/dnd/events/dragdrop-text-elements-input-event-manual.html
https://wpt.live/html/editing/editing-0/contenteditable/spellcheck-insertReplacementText-input-event-manual.html
Flag name on about://flags
None
Finch feature name
InputEventDataTransferForInsertCmd
Rollout plan
Will ship enabled for all users
Requires code in //chrome?
False
Tracking bug
https://issues.chromium.org/issues/401593412
Estimated milestones
Shipping on desktop | 143 |
Shipping on Android | 143 |
Shipping on WebView | 143 |
Shipping on iOS | 143 |
Anticipated spec changes
Open questions about a feature may be a source of future web compat or
interop issues. Please list open issues (e.g. links to known github
issues in the project for the feature specification) whose resolution
may introduce web compat/interop risk (e.g., changing to naming or
structure of the API in a non-backward-compatible way).
None
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/6715253274181632?gate=5118342993805312