Re: [w3c/clipboard-apis] Support for delayed clipboard data (#41)

@gked : That was the incubation document. We've folded the Async Clipboard API info into the main clipboard spec, so this seems like the best place to track the issue.

@poiru : Do you know how that API works with multiple apps writing to the clipboard?  E.g.:
* App1 writes delayed info into clipboard
* App2 reads general clipboard data
* App1 quits
* App2 tries to read the "delayed" data from the clipboard

>From a quick glance, I couldn't convince myself that it was designed to work outside of a single app managing its own clipboard.

-- 
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/41#issuecomment-289920127