W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2016

Re: [csswg-drafts] [css-ui-4][user-select] value is used value?

From: Koji Ishii via GitHub <sysbot+gh@w3.org>
Date: Mon, 08 Aug 2016 08:11:52 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-238169350-1470643909-sysbot+gh@w3.org>
> for both properties, the computed value is the specified value


> contain+text does the same as what contain does today


> contain+none does the same as none


> contain+all means:...

Yes. The latter case is an additional behavior from the current spec.

> user-select-contain would need an auto value that computes to (or 
behaves as, if you prefer used value time) contain on editable 
elements, and as none on the rest.

I'm ok with it, but a question is if author wants to set 
`user-select-contain: none` to editable elements or textarea. If it's 
not useful, we can just set to `contain` for such elements; i.e.,
input[type=text], textarea, [contenteditable] { user-select-contain: 
contain; }

> we need auto to behave as none on ::before, ::after, ::marker

I haven't tested this yet, is it interoperable today, including Blink 
and WebKit? Is there a test?

Assuming yes, again, if you just want to set to a specific value in 
specific cases, `auto` isn't really needed, you can just set it either
 by UA stylesheet or by code. `auto` computing to different values has
 additional complexity than that, so we'd like to limit it to only 
when it cannot be achieved by other methods.

GitHub Notification of comment by kojiishi
Please view or discuss this issue at 
using your GitHub account
Received on Monday, 8 August 2016 08:12:01 UTC

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