RE: On why we cannot (easily) delete/merge the editing specs

Makes sense. We should keep contentEditabletrue spec and move some of the items from execCommands spec into there.



From: johanneswilm@gmail.com [mailto:johanneswilm@gmail.com] On Behalf Of Johannes Wilm
Sent: Wednesday, January 13, 2016 7:21 AM
To: Aryeh Gregor <ayg@aryeh.name>
Cc: public-editing-tf@w3.org
Subject: Re: On why we cannot (easily) delete/merge the editing specs


Right,
so most of your former spec currently lives in the execCommand spec. That spec has been updated and is alive, mainly because of the Clipboard API people who actually need a small part of execCommand - just not things related to contentEditable.

A little too much has been moved into the execCommand spec. The items you mention about paragraph merging and splitting are at least in part only about contentEditable=True user keyboard/IME input without being related to execCommand. So maybe that could be moved. Once we get there we'll make sure to consult with you, Aryeh!
On 13 Jan 2016 9:41 am, "Aryeh Gregor" <ayg@aryeh.name<mailto:ayg@aryeh.name>> wrote:
On Wed, Jan 13, 2016 at 4:24 AM, Johannes Wilm <mail@johanneswilm.org<mailto:mail@johanneswilm.org>> wrote:
> Eventually we should move some items from the
> execCommand spec (about paragraph merging and splitting, etc.) into this
> document, but one will have to spend some time trying to untangle what is
> what.

I mentioned it before, but I'll add again -- if you want good
paragraph merging and splitting algorithms that (for instance)
correctly preserve formatting, I think you'll wind up having to copy a
large fraction of the contenteditable=true spec.  If you ever manage
to devise some paragraph merging/splitting algorithm that's much
simpler than copying a large fraction of the contenteditable=true
spec, make sure to point me to it, because I might be able to notice
things that it's missing.