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

The css wg did indeed talk about user-select, as I just added it to the level 4 css-ui spec:
http://dev.w3.org/csswg/css-ui-4/#content-selection

Quick note, reacting to https://github.com/w3c/editing-explainer/issues/20#issuecomment-66184716 : user-select: element does not mean select the whole element (that's user-select:all), it means keep the selection within the element. Yes, I know that's a bad name, that's why the spec has an issue on it: http://dev.w3.org/csswg/css-ui-4/#issue-dc2ca3bf

We did not directly discuss the user-select:none / contentEditable=true combo, but for now, what the spec says is that the computed value of user-select on an editing host is always "element", so you cannot have user-select none on a contentEditable=true element. But you can have it on descendants, which may be a problem, since it's not clear what it would do. Authors should probably be free to set it any way they want on a contentEditable=false descendant of a contentEditable=true, but for editable descendants, maybe user-select should always compute to text, or maybe only the none value should be force to compute to text, leaving all and element as they are. I've flagged this as a issue in the spec: http://dev.w3.org/csswg/css-ui-4/#issue-c6afab44

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