Re: [w3c/clipboard-apis] Remove clipboard-read permission (#132)

Sure. The suggested removal of `clipboard-read` here implies [requiring user activation](https://github.com/w3c/clipboard-apis/issues/52) to gate Clipboard read. Therefore, this should break any site that currently doesn't require user activation to read the clipboard.

While we don't know the exact magnitude of the breakage (we don't currently have metrics on clipboard read use without user activation), we do know that:
- .03% of pageloads currently [use](https://chromestatus.com/metrics/feature/timeline/popularity/2369) `clipboard.read()`, and .22% of pageloads currently [use](https://chromestatus.com/metrics/feature/timeline/popularity/2371) `clipboard.readText()`. The subset of these sites that doesn't do so requiring user activation would be broken by this change.
- As of September 2020, 11,088 unique sites made use of the Async Clipboard API, according to the HTTP Archive. This number may be higher now, but also includes sites using clipboard write but not clipboard read, or clipboard read, but with user activation, so may represent more than the complete list of affected sites.
- Remote desktop applications, [including](https://github.com/w3c/clipboard-apis/issues/75) cendio.com, as well as Chrome Remote Desktop, would be broken by this change, as this would disallow them to propagate clipboard updates.

-- 
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/pull/132#issuecomment-712501669