- From: snianu <notifications@github.com>
- Date: Wed, 13 Sep 2023 13:51:58 -0700
- To: w3c/editing <editing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 13 September 2023 20:52:07 UTC
> 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. Make at least one format mandatory to write 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 `beforeunload` event is fired, cancel the callback after a timeout period if the callback hasn't completed yet. When the callback is cancelled, set empty data to the calipboard for that delay rendered format. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/424#issuecomment-1718301084 You are receiving this because you are subscribed to this thread. Message ID: <w3c/editing/issues/424/1718301084@github.com>
Received on Wednesday, 13 September 2023 20:52:07 UTC