Delays the generation of the clipboard payload until it is needed by the target applications. Delayed clipboard rendering leverages the existing Async Clipboard API to allow web applications to improve performance when exchanging large data payloads by only producing the clipboard payload once a target application attempt to access it.
Source applications typically don’t know where the user intends to paste the content at the time of copy, so web applications may produce several formats when writing to the clipboard to prepare for many possible target applications. The generation of one or more representations may take enough time that it is noticeable to the user, but it is unlikely that the target application will need all produced representations.
Delayed clipboard rendering is a new opt-in feature for the async clipboard write() method. If a site doesn't opt-into it, then it will get the existing behaviors. For sites that do opt-in, it would require changes in the ClipboardItem IDL, so it would throw error on browsers that do not support this feature.
None.
None.
https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/DelayedClipboard/tag-security-privacy-delayed-clipboard-rendering.md https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/DelayedClipboard/DelayedClipboardRenderingExplainer.md#privacy-and-security-considerations
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
No.
The Async Clipboard API have tooling support as described in the DevTools support checklist.
No milestones specified