Re: [editing-explainer] define relation to HTML Editing APIs (#48)

> But I am slightly less sure about the division: When you say "cE should be an independent spec" -- you mean the "contenteditable=typing" specification that we are working on here, right? In the CSSWG F2F meeting, the above linked specification was referred to as the "contenteditable spec" just yesterday. This is somewhat confusing and it should be made clear what is what.

IMHO, the "Editing Task Force" should centralize everything around editing. At a first stage, it would be translated into the following tree of specs:

 * Editing
   * ContentEditable
     * cE=true
     * cE=typing
    * Editing Commands (execCommand & co.)

There are also other specs that are very related to editing but not exclusive to it:
 * Selection (should it be inside Editing as well???)
 * Ranges
 * Clipboard

I assume that there will not be much love for cE=true and Editing Commands for now, but the other specs are the hot topics we should be focused at the current stage.

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