Re: [w3c/editing] Seeking feedback on Clipboard Pickling APIs. (#334)

I'm having a trouble understanding what's being proposed here. Conceptually there are two things:
 1. Website accessing data in the system pasteboard/clipboard provided by native applications
 2. Native applications accessing data website has written that's normally exposed natively (e.g. png, psd, docx files)

Per prior discussion, for (1), native applications must opt-in to expose information to web apps directly. So, solving this problem requires some kind of agreement between native applications and web browsers to do this.

Looks like this proposal is saying that we'd let web app specify `unsanitized` option to retrieve this? Is this to protect websites from receiving potentially harmful (e.g. HTML with scripts) content? But if there is some malicious native app on user's machine, that application can do whatever it wants to do with any website, right? I'm really failing to see what this option is for.

For (2), native applications need some mechanism to access the data which isn't usually available to them.

The proposal also suggests adding ability to write unsanitized version of things. Again, I'm unsure why this is needed. Why can't the browser always make unsanitized version available to native apps which request it? Why does a website explicitly need to request this?

So again, I'm failing to see any need to add Web API for both use cases. Like we've repeatedly stated in the past, Apple's WebKit team believes this is a domain of the operating system design. If these use cases are important, then we'd likely introduce new API at OS level (I'm neither confirming nor denying we may or may not do this).

-- 
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/334#issuecomment-908642291