Re: [w3c/clipboard-apis] What happens if promises to Blobs are not resolved within a reasonable amount of time? (Issue #161)

> @tomayac The tab focus is a bit complicated issue. There could also be two tabs racing to write content to the clipboard if the user (for some weird reason) switches back and forth in quick succession(using ctrl+tab & ctrl+shift+tab) and initiates copy from both tabs. I discussed this with @BoCupp-Microsoft and we think we need a mechanism to store the `ClipboardItem` somewhere in the `Document`, and based on which tab has focus, we will write the `ClipboardItem` fetched from the focused `Document` to the clipboard. The list will also be helpful if the web authors write multiple `ClipboardItem`s in a loop (I know this is a contrived scenario, but just wanted to mention it for completeness). The last `ClipboardItem` that was set by the web author before the write to the clipboard is initiated, wins. Please let us know what you think as we need more feedback from web authors to come up with a valid algorithm.

That proposal seems confusing for end users. I think they should be informed clearly when a write operation starts, is going on and has ended. Two write operations should not be allowed to overlap. If there's indeed a time intensive `write*()` going on and an end user wants to start a different one, the first one should clearly be aborted.

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