Re: [editing] Reference actions in clipboard API spec for execCommand copy/cut/paste (#61)

@johanneswilm see http://www.whatcouldbewrong.com/articles/html5-clipboard-support/ for a higher-level overview of how it's supposed to work now. This appears to have wide agreement among browser vendors (in fact implementations are underway in both Blink and Gecko), so it's considered safe enough. I'd also personally like to see some permission configuration that would allow sites to use *execCommand('paste')*, but I'm not holding my breath..

As you see, the solution for the "custom copy/cut/[paste] buttons" use case depends on document.execCommand(). If you're serious about "deprecating" it you may want to come up with an alternative way to do it.

(Now, I know that I haven't followed your discussions - and I've done enough QA on rich text editing functionality to know that it's complex - but it seems like this group simply concluded "the rich text editing stuff that browser vendors spent years and years developing and testing isn't good enough yet, so let's throw it away and make an API that lets JavaScript authors tackle all that complexity instead, because given yet another set of events to intercept will let them implement all the logic required for rich text editing in JS". Given the stunning amount of work Aryeh Gregor put into documenting what we've already got, the complexity of writing a good editor implementation and the fact browsers have spent so many years developing and testing already, this seems like an odd approach to me.)

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/61#issuecomment-127405108