[w3c/editing] Seeking feedback on delayed clipboard rendering proposal (Issue #417)

Delayed clipboard rendering is the ability to **delay the generation of clipboard data until it is needed by the target applications**. It is especially useful when the clipboard formats supported by target applications are expensive to produce. Delayed clipboard rendering enables web authors to specifically mark delayed rendered payloads in the source application and avoid producing them if they’re not requested by target applications. Our goal is to **leverage the existing Async Clipboard API to allow websites exchange large data payloads and improve performance by only producing clipboard payload when it’s needed** by target applications.

We detail the proposal in this [explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/DelayedClipboard/DelayedClipboardRenderingExplainer.md).
We would love to get feedback on our [proposed solution](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/DelayedClipboard/DelayedClipboardRenderingExplainer.md#proposed-solution-map-of-mime-type-to-promise-in-clipboarditem-constructor), [considered alternatives](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/DelayedClipboard/DelayedClipboardRenderingExplainer.md#considered-alternative-map-of-mime-type-to-promise-in-new-method), and [open questions](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/DelayedClipboard/DelayedClipboardRenderingExplainer.md#open-questions). 

Related discussion: https://github.com/w3c/clipboard-apis/issues/41


@snianu @sanketj 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/417

You are receiving this because you are subscribed to this thread.

Message ID: <w3c/editing/issues/417@github.com>