You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?