Re: [ui] time to re-introduce the 'user-select' property to the spec?

On Tue, Jul 24, 2012 at 1:47 AM, Edward O'Connor <> wrote:
> I'd like it if we could at least get the currently-interoperable subset
> ("none" and "text", though it'd be nice to get "auto" as well) into
> whatever level of CSS UI would be appropriate. We're also looking at
> adding an additional value, "atomic", to WebKit's implementation. As
> Alice said in [5],
>> We intend to work on an experimental implementation of a new
>> -webkit-user-select value that we are calling "atomic". This value
>> causes the element to which it is applied to behave atomically for
>> selection purposes; either all of none of the element and its contents
>> are contained in the selection.
>> [Gecko has] a value, "all", that superficially behaves like "atomic",
>> but has some different behavior under incremental selection, which is
>> why we're not using that value.

I'd be very interested to hear what the issues are here.  It might
make more sense for Gecko to change its behavior instead of us
introducing a new value.  There are known behaviors in Gecko that are
simply bugs -- like off the top of my head,

Received on Tuesday, 24 July 2012 08:07:10 UTC