[css-ui-4] Deal with locked editable elements and user-select #285 #2961
Conversation
|
This clarifies what is supposed to happen on form controls when they're in read-only mode. As per #285 (comment), this does not attempt to prevent We could have all values compute to |
| <li> | ||
| on <a>locked editable element</a>s | ||
| where the computed value is ''user-select/contain'' | ||
| if the specified value was ''user-select/text'' or ''user-select/auto'' |
There was a problem hiding this comment.
As far as the handling of auto for this case is mentioned below, it can probably be removed here.
| A <dfn>locked editable element</dfn> is | ||
| a normally <a href="https://www.w3.org/TR/html/sec-forms.html#mutable">mutable</a> form control with textual content, | ||
| when it is placed in a non mutable state, | ||
| such as a <{textarea}> with the <a href="https://html.spec.whatwg.org/multipage/input.html#the-readonly-attribute"><code>readonly</code></a> attribute. |
There was a problem hiding this comment.
It seems to me that this definition is probably not clear enough, for example, it is unclear whether a disabled form control is a "locked editable element". I guess the ambiguity is from "normally mutable form control". Is a disabled form control considered normally mutable? Or is being disabled just a non-mutable state?
Maybe explicitly referencing readonly attribute rather than listing it as an example may help? Something like "a otherwise mutable form control ... when it is placed in a non-mutable state by readonly attribute".
Closes #285