- From: Alex Gough <notifications@github.com>
- Date: Mon, 25 Oct 2021 17:31:19 -0700
- To: w3c/editing <editing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 26 October 2021 00:31:32 UTC
Continuing this for Chrome: Looking over this issue I see a couple of areas that might be addressed but... the set of documents is quite sprawly. Feel free to point to answers that I have missed! 1) "And that format must not be something that existing software will eagerly decode and deserialize — it should be simple, yet opaque to existing software." - is this format documented, why do we think existing system apps won't try to parse it? 2) How is Chrome making sure that unsanitized data doesn't get to system apps? (i.e. how is Chrome going to write the clipboard data on Windows, on other platforms?) -- 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/editing/issues/315#issuecomment-951446764
Received on Tuesday, 26 October 2021 00:31:32 UTC