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

I'd like to add some thoughts from the developer's perspective.

At the moment pasting any image from Word requires some hacking to retrieve the pasted content. We, CKEditor 4 and CKEditor 5, and probably others use RTF format, which is available for pasted Word content. Basically, we had to implement a simple RTF parser for it. Yet the whole approach is very error-prone, e.g. sometimes images are present in RTF but not in HTML (and vice-versa), some images in RTF are stored in unsupported formats, like WMF, etc.

That's why such a change will be much welcomed by everyone who ever tried to implement pasting images from Word (well, at least by me!). The whole process of importing pasting images would be much simplified and, at last, it would be the same in every browser (as Safari does not expose RTF format in the clipboard data). That's also another advantage of standardizing Safari's approach (at least from the developer's perspective): implementations are already here. RTEs that support pasting images in Safari will probably support the proposal out of the box.

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