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

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. So combined with the use case from @rniwa, it looks like, as Ben suggested, all the following values are equal if within cE=true/typing:
* cE=false
* user-select:none
* user-select:all
* user-select:element

and 'user-select:none' can actually be selected and deleted if within cE=true/typing. Is this correct understanding?

And, as we allow cE=true inside cE=false inside cE=true to be selectable/editable, do we want the 'user-select' to be similar? I actually hope not, but I'm open to others.

The CSS WG put the 'user-select' property deferred to CSS UI Level 4 and wish inputs from this TF. I'm not sure how much we want to discuss/define behavior of the 'user-select' outside cE=true/typing, but I think we should make a recommendation of the behavior within cE=true/typing at least.


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