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

> > However there were feedbacks from web developers that if it's gated behind user gesture requirement, then it would be too restrictive and fetching payload (which might be huge) from the server and writing into the clipboard might cause performance issues during copying/pasting.
> 
> Is this still under discussion somewhere? I don't understand how this can be reconciled with the need to keep users' clipboard contents private when they visit a web page (which is related to one of our key design principles : https://www.w3.org/TR/design-principles/#safe-to-browse that it must be safe to visit a web page).

There was a discussion on github which can be found [here](https://github.com/w3c/clipboard-apis/issues/52). 
To be clear, it is not just a random site accessing clipboard content. User will need to give clipboard access to the site through permissions API first. 
In addition, having a [sticky user activation](https://html.spec.whatwg.org/multipage/interaction.html#sticky-activation) requirement (instead of [transient](https://html.spec.whatwg.org/multipage/interaction.html#transient-activation)) and an active document in focus would ensure that the webpage doesn't have access to clipboard without user explicitly interacting with the web page at least once.

We are reaching out to web applications so they can weigh-in on this bit as well.

CCing @garykac as FYI


-- 
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-853319479