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

I think -- well, I'm not familiar with the history, sorry in advance if I'm wrong, but -- the idea of contentEditable='typing' is that it's the best method to make editing interoperable. If we ignore this for now, and sites started building on top of one implementation within contentEdiable=typing, how could we make it interoperable later on?

If there were specific commands developers want to use within contentEditable=typing, I'd be happy to allow them. But again I'd like such commands have good interoperability, I'd like the list of commands white listed and spec'ed so that browser developers can make them interoperable.

Well, I understand spec'ing them is hard, but not allowing is quite easy. Do you have specific reasons you want to allow it, and idea how to make it interoperable later on? 

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