Re: [editing-explainer] ContentEditable with UserSelect=None needs to be documented (#20)

@johanneswilm 
>> A discussion in this TF said that cE=false within cE=true/typing should treat it as an atomic block that can deleted by BACKSPACE/DELETE.

> That is probably true, and I would suggest one does this in a standard contenteditable environment, but if we do not handle deletion of content at all in contenteditable=typing, then does it matter how it is treated?

I don't remember the conclusion, sorry not reading the spec these days, but if we concluded so for deletion, that's fine. Are we not defining any default handlers for these intents? No default handles for arrow keys too?

The original intention of this issue is that I just want the behavior clearly defined, so if the spec defines no default handlers, things should be easier.

Other possible questions are like:
* Are we also disabling all mouse selections and let JS to handle? If so, can you clarify that?
* When JS sets the selection to user-select:none, what would happen?
* When JS sets the selection to a text node, but then JS applied user-select:none, what would happen?
* When an element has user-select:none, but one of its descendants have user-select:all, what are the expected behavior?

I suspect the current behavior is very much non-interoperable. I hope we can make it interoperable at least within ce=typing elements.

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