Re: [w3c/editing] contentEditable: clarification of selection and typing behavior (#156)

> Or what do you think @Reinmar?

Yes, fixing `execCommand()` would be a waste of time. No sane RTE uses it.

> Or which editors are you thinking of that let the browser handle uncontrolled DOM-changes (without time traveling backward)?

Hard for me to tell, because I don't know anything specific about any other editor than CKEditor, but I'd presume that all RTEs without a custom data model (and perhaps, to some extent, even some with custom data models) let the browser insert and delete text without much control. In other words – these RTEs behaviour would change if browsers would change their "type over" behaviour.

The group of editors with custom data models is pretty small (it's a great minority in fact), because developing such an RTE is extremely hard and long process. The one I know of are CKEditor 5, Quill, ProseMirror, Draft.js and Trix. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/156#issuecomment-263938831