W3C home > Mailing lists > Public > www-style@w3.org > December 2014

Re: [css3-ui] bringing back 'user-select' (issue 50)

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 4 Dec 2014 15:54:25 -0800
Message-ID: <CAAWBYDDAJ2DyqtjVcA74cv-B0y-nZ=sFR4GYfc08wBFF3YdOiQ@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: Florian Rivoal <florian@rivoal.net>, www-style list <www-style@w3.org>, Tantek Çelik <tantek@cs.stanford.edu>, "Edward O'Connor" <eoconnor@apple.com>
On Thu, Dec 4, 2014 at 3:50 PM, fantasai <fantasai.lists@inkedblade.net> wrote:
> On 11/26/2014 10:30 AM, Tab Atkins Jr. wrote:
>> On Wed, Nov 26, 2014 at 10:10 AM, Florian Rivoal <florian@rivoal.net>
>> wrote:
>>> Finally, are we sure this is really a good idea?
>>
>> Yes, it's a useful property.  "none" is great for doing manual
>> drag-and-drop or the like.  "all" is useful for implementing "atomic"
>> elements that should only be selected whole.
>
> These are useful things, sure, but doesn't this belong in the content layer?
> It's not about style. It is, afaict, another one of those content-layer
> things
> that someone made into a CSS property for the convenience of using CSS
> selectors.

Not really.  It's nothing to do with the semantics of the content.  It
is a control over how the element behaves in a certain context, but in
a general, simple way that I think is appropriate to view as under the
"style" aegis.

~TJ
Received on Thursday, 4 December 2014 23:55:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:49 UTC