Re: [w3c/editing] Should we modify the clipboard API spec to match Safari's behavior for HTML-referenced media? (#285)

Implementation wise, having the option on ClipboardItem.getType rather than Clipboard.read does seem somewhat problematic though. Currently the "getType" call doesn't do any processing, and certainly doesn't call out to the browser process. To implement the proposed transformation in a secure manner the transformation can't be done entirely renderer side, since we can't trust the renderer process to accurately portray what file URLs were on the clipboard (on the other hand, parsing the html that was read from the clipboard in the browser process isn't a good idea either).

Re the DataTransfer interface, adding a flag to getData seems somewhat odd too, given that that is documented as the "old" interface. The new interface would be DataTransfer.items I think, but there wouldn't really be a good way to add a flag there? I don't really have better suggestions either though.

-- 
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/285#issuecomment-818447304