Re: [w3ctag/design-reviews] Async Clipboard - image/delayed content (#350)

Sorry for the slow reply. Guess we don't have updates from the last meeting.

On the transcoding front, I don't understand how this will work for professional productivity apps. Lossy transcoding is surely going to not fly for, e.g., image editing apps. What is their recourse? A separate permission requesting lossless access? Custom datatypes? Something else?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/350#issuecomment-497449039

Received on Thursday, 30 May 2019 19:10:33 UTC