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

@fredck @hallvors You should look at this as well.

Basically, we need to have some coordination of execCommand. We cannot both say that:

> If an implementation supports the document.execCommand method and allows calling it with the commands "cut", "copy" and "paste", the implementation must trigger the corresponding action, which again will dispatch the associated clipboard event.

and

> In other words, execCommand should not be a feature of cE, but a document feature... and sincerely, it should not dependent on cE at all... it should just take the current selection and execute the requested command on it, period. (I mean, even in non cE selections)

If we also want cE=typing to work with user intents in which we want the site to be able to control what action is triggered upon user intents (or no action at all if no action is defined).

@hallvors How about we specify that the things mentioned in the clipboard api in relation to editable elements are only true for designMode and the current contentEditable, but not contentEditable=typing? Where would we need to discuss that?

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