- From: Paul Libbrecht <notifications@github.com>
- Date: Thu, 10 Mar 2022 08:53:04 -0800
- To: w3c/editing <editing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 10 March 2022 16:53:17 UTC
Thanks @snianu : I am still not convinced by the 100 limit but it will not be a fight subject. I understood it was per origin but the log seems to discuss it differently. > So, attack vector is that two origins use different custom formats to communicate. (Similar to socket connections.) I didn't understand that one. >> Finally, would the set of (web and desktop) apps that have been visited by a user not be something useful for the user itself? > I don't think I understand the question. Are you asking what happens if the destination app doesn't have support for the custom format copied from another app? The answer to this question is, custom formats by definition are not readable by apps that don't have support for it. Nope. I am asking if there could not be a UI offered/conceived/discussed at browsers or OSs that say: "Ah, you have a clipboard-pickle of type zzz; you could open it at the website x/a/b and using app zz/zz." This is done with files currently (and not always very well performing). -- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/393#issuecomment-1064281363 You are receiving this because you are subscribed to this thread. Message ID: <w3c/editing/issues/393/1064281363@github.com>
Received on Thursday, 10 March 2022 16:53:17 UTC