Re: [w3ctag/design-reviews] ClipboardChange event API (Issue #1017)

torgo left a comment (w3ctag/design-reviews#1017)

Hi folks - we discussed in our plenary call today and agreed on this comment which has been collaborated on by the the group, with notable input from @dandclark, @martinthomson:

The TAG is happy to see the changes made to include only the clipboard data types in the event (and only the types, rather than the full clipboard contents). We believe that the use of types is sufficient to give applications the information they need to satisfy the use cases in the [explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/ClipboardAPI/clipboard-change-event-explainer.md), without the risks that involved with granting full clipboard access. The existing Chromium model of using permissions to gate full read access to the clipboard is not necessary to satisfy these use cases, and we consider it to be unsafe: it's too easy for sites to gain and to maintain full clipboard access in a way that's not always clear to users.

But we believe that the current state of this proposal does not worsen that use of permissions, and in fact offers a path towards improvement. By granting access to the data types only, some scenarios that today would require full clipboard access could now instead be implemented in an interoperable way without a problematic use of the permission model.

That said, the other protections mentioned are still important and should not be loosened. Namely, the requirements that the document have focus to receive the event and that multiple clipboard changes occurring while the document does not have focus must be coalesced to a single event with only the current state at the time the document regains focus. An additional requirement we feel is important is that the event should only be fired if the document has achieved the [sticky activation](https://developer.mozilla.org/en-US/docs/Glossary/Sticky_activation) state.

So we are closing this as satisfied, and we encourage further exploration of how dependence on long-lived clipboard permissions can be scaled back in an interoperable way.

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

Message ID: <w3ctag/design-reviews/issues/1017/2774608569@github.com>