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

I certainly don't want to take on a spec to work on in my free time by myself forever. And I agree that the above specification is a lot about describing already available behavior.  

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.

As for execCommand: I understand there are two different ideas about how to use it here. Whether or not it should need an editing host seems to be a decision that needs to be taken by the relevant working group at some point of time, and then all the documents should be in agreement about how they treat it. It makes no sense for us to treat execCommand as something that works in one way, when another specification claims it works differently.

It seems to me that what is needed now is that both the cE=typing and the above linked spec are put into shape and that we have a meeting of some kind that is able to reach decisions (by vote if necessary) on the parts where there is disagreement. A specification can continue to evolve over a long period of time, so we don't need to put a final stamp on the above linked spec, but if we reach clarity on some fundamental issues and edit the draft specification accordingly, we will have much less confusion.

So it seems to me that we should A) ensure that the above specification has an active editor for the time being who is able to do at least minor but fundamental changes to it, B) Preferably have all the editing specs in the same task force/working group, C) Continue to edit the specs and collect divergent ideas here on github, the mailing list, etc. D) Have a meeting (F2F or over phone) in which we can make decisions on all the issues where there are controversies.

That way, I think, we should quickly be able to get to a state where the cE=typing spec draft has reached a level where it begins to be something one can refer to confidently.  

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