Re: [editing] inputType should be tied to the command names and having that tied to a way of declaring what you support (#110)

@gked: Ok, so we are going back to using execCommand? Will we define how the execCommand commands works?

I think the most important for webapps is to have a way to make all extra content menus go away - easily. Secopnd priority is to make just the content menus used in Safari go away (= the ones that go beyond the clipboard actions).To tie that in with defining all of execCommand may not be so helpful, as it may take decades to really fix all of execCommand, and there is some chance that it may never happen.

But if you feel you can standardize execCommand behavior and make it configurable, I don't want to discourage you from working on that. Just don't postpone the option to make all the menus go away until after you are done, because that's quite urgent to have fixed right away.

I think spending some time on finding out how to turn everything off is a good idea for the next F2F. It would be good to have proposals at that time on how to do that. Just a very simple "All execCommand commands requirering an editing host and all extra menus are turned off by default on cE=events" would be good enough for most JS editors, I think.  So if browsers don't like that idea, maybe you could come up with an alternative proposal?

Anything beyond turning everything off would be great if you can make it happen, but it's not really essential to make an editor and may end up not being used by editors who prefer implementing actions themselves and drawing their own menus. 

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