- From: snianu <notifications@github.com>
- Date: Tue, 31 Oct 2023 14:47:34 -0700
- To: w3c/editing <editing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 31 October 2023 21:47:40 UTC
@snianu commented on this pull request. > @@ -248,6 +191,9 @@ This requirement is now enforced for the Async Clipboard API overall. It may be ### Permissions Due to concerns regarding permission fatigue and comprehensibility, and due to the limited utility of a permission, no new permission would be implemented for unsanitized clipboard. Given that Clipboard API read and write are already permitted, unsanitized clipboard read and write will be permitted as-is. +## Alternatives considered +Web custom formats can be used to exchange unsanitized HTML if both source and target apps have support for it, but there are many native apps that don't have support for web custom formats, so contents copied from these apps in the HTML format would have to go through the Browser sanitizer in `read()` that would result in loss of fidelity. Done. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/pull/456#discussion_r1378195813 You are receiving this because you are subscribed to this thread. Message ID: <w3c/editing/pull/456/review/1707287115@github.com>
Received on Tuesday, 31 October 2023 21:47:40 UTC