W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2018

Re: [csswg-drafts] [css-ui-4] Deal with locked editable elements and user-select #285

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Sat, 28 Jul 2018 15:29:08 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-408615443-1532791747-sysbot+gh@w3.org>
This clarifies what is supposed to happen on form controls when they're in read-only mode.

As per https://github.com/w3c/csswg-drafts/issues/285#issuecomment-397404205, this does not attempt to prevent `user-select: none` or `user-select: all` on such things, but does make sure that `user-select: auto` and `user-select: text` do the same thing as `user-select:contain`.

We could have all values compute to `contain`, but allowing `none` and `all` seems useful and not particularly hard, if that's OK with implementers.

GitHub Notification of comment by frivoal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/2961#issuecomment-408615443 using your GitHub account
Received on Saturday, 28 July 2018 15:29:13 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:33 UTC