- From: snianu <notifications@github.com>
- Date: Tue, 21 Mar 2023 15:28:49 -0700
- To: w3c/editing <editing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 21 March 2023 22:29:02 UTC
@snianu commented on this pull request. > @@ -0,0 +1,257 @@ +# Unsanitized HTML for Async Clipboard API + + +## Author: +* ansollan@microsoft.com +* snianu@microsoft.com + +## Introduction +Using DataTransfer object’s setData and async clipboard write method, we are seeing interop differences in how the HTML content is sanitized and written to the clipboard. In Chromium async clipboard write method clears the clipboard content first and then writes the payload which results in overwriting the previous HTML content that was inserted by authors using DataTransfer object’s setData API. It’d be beneficial for the web authors if async clipboard and setData APIs provide the same HTML content during copy operation so round tripping is possible without any interop differences. I can add a note here if that would be helpful, but I'm not sure if I know enough to talk about the implementation of other browsers. I'll remove the Chromium implementation details. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/pull/420#discussion_r1144051254 You are receiving this because you are subscribed to this thread. Message ID: <w3c/editing/pull/420/review/1351475138@github.com>
Received on Tuesday, 21 March 2023 22:29:02 UTC