Re: [editing] What to do with contentEditableTrue? (#54)

I think you summarised it well. To make cE=true usable, we need the following:

 1. Quality behavior spec’ed.
 2. Interoperability
 3. Hooks for overriding the behavior.

One of the ideas that made cE=typing was that cE should be “modular”. It means that “typing” was one of the modules but we could have others. In this way one could have contenteditable=“typing newline delete etc”, enabling a series of editing modules. Each module could be spec’ed independently. Finally, cE=true could be simply spec’ed as a shortcut to have all modules enabled.

I’m for spec'ing cE=true to make it useful and I like the modularization idea. 

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