Re: [editing-explainer] Should execCommand be spec'd to do nothing in cE=typing? (#33)

I think I understand where we misunderstand each other. I was talking about when developers wanted to use execCommand in a new code base written for cE=typing, there's nothing that prevents or even discourage doing so. You worry that, if we prohibit that, we have to implement all commands to fail, correct?

How about this:
> When the selections contain `contentEditable=typing`, `execCommand`, `queryCommand`, (etc., fill in others) may not work as they do in other elements, or may even fail to execute. These methods are not interoperable and their uses are strongly discouraged.

I agree that the cost to make sure they fail is worthless, but without spec saying anything, I think natural expectations are these methods work well. I'd like to avoid such expectations, and we may end up seeing bugs wanting execCommand to work the same way as in, say, IE.

If I understand correctly, I'd like to prevent both from happening, and I wish the spec to have text to clarify that.

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