Re: [w3c/editing] [Delayed Clipboard Rendering] What happens to the clipboard data on Tab/Browser Close? (Issue #424)

> > Created [a document](https://docs.google.com/document/d/1H6ow7RWa4MeycKP3OQBoMhLuMaJct3jSCWW6apcVu9U/edit?usp=sharing) to discuss these options in more detail. Please let us know if you have any comments/concerns.
> 
> We want to discuss the options listed in the above document, but want to propose the following option which is sort of a hybrid of options 2 and 4:
> 
> 1. At least one built-in format must be written to the clipboard without delay as part of the write operation so there will be some data on the clipboard (could be a low fidelity `text/plain` format) if the browser/tab closes and the site doesn't get a chance to generate the data for the delay rendered formats within the timeout window. If the site only writes one format to the clipboard, then it can't be delay rendered.
> 2. If a delay rendered callback is already running before the page unloads, cancel the callback after a timeout period if the callback hasn't completed yet. When the callback is cancelled, set empty data to the clipboard for that delay rendered format.

@evanstade @inexorabletash If this addresses all your concerns, then we can mark it as resolved for now unless we discover something in the future, then we can reopen it. WDYT?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/424#issuecomment-1719093495
You are receiving this because you are subscribed to this thread.

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