Re: [editing] "CE Events Container" should be replaced by "editing host" (#66)

> For the purpose of writing a spec, I don't think we want two different terms.

We need to distinguish between those editing hosts which can serve as editing hosts for execCommand and those that cannot serve as editing hosts for execCommand. The one in cE=true can serve as such an editing host, whereas those in cE=events cannot serve as such an editing host. 

One solution A) would be to not use the term "editing host" for cE=events containers. Another solution B) would be to call them two different types of editing hosts.

> You can have contenteditable=events inside contenteditable=true.

True. Given that the ultimate goal is to eliminate cE=true, I think the best is to keep the definition as simple as possible. Something like "Any element that has the contenteditable attribute set to true that is a descendant element of an element that has the contenteditable attribute set to events will be treated as if it its contenteditable attribute is set to false."

Just one example. I don't really care for how to handle that case, as long as the definition is simple and not open to ambivalence.


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