Re: [editing-explainer] execCommand has now been spec'd to trigger a "User Intent" for cut/copy/paste (#47)

Hi, to be honest I'm not well informed about what you are working on here. But it seems like you insert a new sort of event handling ('intents') into the process of editing text, and then sort of re-use execCommand() with new actions like "new line", "delete"?

Why are you re-using execCommand() if you don't even want to spec it completely?

>From the perspective of the clipboard events spec, it doesn't matter at all whether designMode or contentEditable is enabled. If you run document.execCommand('copy') without either, per spec the copy event must fire. No selection? It still fires. 

And yes, the copy/cut/paste events seem quite close to your "intents". Is it possible to trigger such intents from, say, a <button> element?

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