MicrosoftEdge / MicrosoftEdge/MSEdgeExplainers

[Delayed Clipboard Rendering] How should dynamic content changes be handled?

Open
#612 2 comments 0 reactions 1 assignee View on GitHub

@anaskim is already working on this.

Since Nov 21, 2022.

Delayed Clipboard Rendering
Dominant language
HTML
Stars
1.4k
Forks
286
Avg merge
3d 1h
Merged PRs (30d)
8

Description

With delayed clipboard rendering, serialization of the copied content is differed until it is actually needed. However, the content may change - ex. due to DOM mutations, style changes - after it is copied, but before it is pasted. How should copy serialization work when this happens?

Some thoughts:
If we undefer (ie. generate the clipboard data) as soon as a conflicting content change happens, this would prevent information loss, but may negate any benefit that delayed clipboard rendering provides.
If we continue to defer and perform a "live" serialization when requested, will the serialized content be useful to the user? Also, do we need a range object to keep track of the part of the page that was copied?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.