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

Take this is my personal opinion at this point, but I'm still in favor to disable it. I'm open to how to disable it, from ignoring to throwing.

I have no idea how Gecko/IE implement execCommand(), but I'm guessing there will be a lot of work for all UAs. Consider JS sets the selection to an element with display:none. Or, anchorNode pointing to cE=false. Since at least WebKit/Blink used to normalize such selections when they're set, execCommand has never received such selections as input. What execCommand should do, and whether queryCommandEnabled should return false or not for such selections are completely new behaviors.

And the history tells me that if we do it without specs and were not interoperable, someone will file bug reports saying "I consider this UA doing that way is the right thing." Isn't that what we're trying to get out from?

We had a history of our non-interoprability troubled developers and users so much. Maybe it's my false fear, it may be quite easy to upgrade all execCommands to new behaviors, but we could allow it anytime if we want to. Without concrete needs expressed, I'd prefer to start from the minimum and prioritize us on interoperability.

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