Re: [w3ctag/design-reviews] Pickling for Async Clipboard API (#636)

Thanks, @torgo for sharing TAG consensus!

Correct me if I am wrong but its sounds like security scenarios presented are applicable to not just pickling but any format used by async clipboard api. Pickling format in itself doesn't create any additional vectors of attack in this case.

We are reaching out to security reviewers that have reviewed async clipboard api before it was shipped, to better understand rational behind the current API design. 

P.S. We took your feedback about "sticky" activation and moved to requiring "[transient](https://html.spec.whatwg.org/multipage/interaction.html#transient-activation)" activation for reading and writing to the 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/w3ctag/design-reviews/issues/636#issuecomment-859967433