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

Hey guys, can we get some kind of resolution on this? Everyone seems to agree that we don't want to spec out the different execCommand methods right now and we might not ever support any of them inside cE=typing. 

It's always easier to add functionality later on rather than remove it, and I don't think the proposals here really diverge much. About we add this text to the spec text under contenteditable="typing": 

> `execCommand` and `queryCommand` should not affect elements that are editable because they or one of their ancestors has their contenteditable attribute set to "typing".

If we want to be more permissive at a later stage, we can always change that with a white list, etc. . We just need to have a solid minimum now.


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