Seeking feedback on delayed clipboard rendering proposal
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 202
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
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.
We would love to get feedback on our proposed solution, considered alternatives, and open questions.
Related discussion: https://github.com/w3c/clipboard-apis/issues/41
@snianu @sanketj
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the DelayedClipboardRenderingExplainer.md proposal, especially the proposed solution, alternatives, and open questions. Then review the related w3c/clipboard-apis issue and existing discussion; this issue is complete when informed feedback on the proposal is provided, rather than when a code change is made.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100