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

Let us first observe that allowing execCommand doesn't cause any interoperability issues as long as authors don't manually call execCommand since cE=typing doesn't trigger any execCommand by user actions such as inserting a new paragraph, or deleting the selection, except inserting a new character.

Now notice that even if we "disallowed" execCommand inside cE=typing, authors can always override the contenteditable attribute to "true" temporarily and call execCommand with arbitrary arguments.  So there is no way for us to "prevent" authors from having interoperability issues if they decide to use execCommand.  And they can always decide to use execCommand at any moment because there is nothing that prevents authors from overriding contenteditable attribute.

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