- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 Aug 2016 07:15:07 +0000
- To: public-css-archive@w3.org
Can you clarify if my understanding is correct? - 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: - if you are starting the selection from outside of the element, the same as `contain` today - if the selection would start from inside the element, select the entire element, but do not allow extending the selection outside of it Is that right? I'd need to think deeper about this, but based on this first read (and bikeshedding aside), I think this might work. A couple things we would probably need to tweak, though: - 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. - user-select may also need to take an `auto` value. It wouldn't do the magic inheritance thing of today, but: - all implementations have it - we need `auto` to behave as `none` on `::before`, `::after`, `::marker`, unless we want to break compat and make these things selectable by default, or deal with that in the UA stylesheet. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/336#issuecomment-238158665 using your GitHub account
Received on Monday, 8 August 2016 07:17:15 UTC