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

I'm supportive of this proposal as long as we can address the memory leak issue, perhaps by only generating blobs if needed (during paste event handlers?), or otherwise removing them after some time (after a paste event is over, if the site hasn't taken them yet?).

If we can't fix the memory leak issue, another way to approach this issue (reading HTML referenced media) could be to base64-encode the image and include it rather than referencing it in the HTML payload. That said, this approach would likely only work for a small set of often-used formats (like images), and encoding can take significant time, so I'd still prefer either the specified or webkit-implemented approaches discussed in the first message.

-- 
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-797847743